See llms.txt for all machine-readable content.

Back to Templates

Hash and sync leads to Meta CAPI with DevDeskApp, Google Sheets, and Slack

Created by

Created by: Devdesk App || devdeskapp
Devdesk App

Last update

Last update a day ago

Categories

Quick overview

This workflow receives lead data via a webhook (or a manual test lead), normalizes and SHA-256 hashes the email with DevDeskApp, generates a deduplication event ID, formats a Meta Conversions API payload, then sends it to Meta Graph API while logging the lead to Google Sheets and notifying Slack.

How it works

  1. Receives an inbound lead from the Production Lead Ingestion Webhook (or generates a sample lead when run manually for testing).
  2. Cleans and lowercases the lead email using DevDeskApp to meet Enhanced Conversions formatting requirements.
  3. Hashes the normalized email with SHA-256 and generates a UUID event ID for conversion deduplication using DevDeskApp.
  4. Builds a campaign tracking slug from the campaign name and city and formats a Meta Conversions API (CAPI) event payload.
  5. Sends the server-side conversion event to the Meta Graph API endpoint.
  6. Appends the privacy-verified lead record (including hashes and event ID) to a Google Sheets tab.
  7. Posts a Slack message to alert the marketing team with the campaign, event ID, and SHA-256 digest.

Setup

  1. Configure the Production Lead Ingestion Webhook URL in your form/landing page tool (or other source) to send lead payloads to this workflow.
  2. Add and configure the DevDeskApp node credentials (or ensure the DevDeskApp community node is installed) to use the text and crypto operations.
  3. Update the Meta Graph API request with your Facebook Pixel ID and provide a valid CAPI access token/authorization for the HTTP request.
  4. Connect Google Sheets credentials and set the correct spreadsheet ID and sheet name (for example, the Verified_Leads tab).
  5. Connect Slack credentials and set the target channel (for example, #growth-marketing-alerts).