API & Webhook Trigger — Developer API Key Authentication

The workflow builder's API/Webhook trigger node now authenticates with a Developer API key instead of a per-campaign webhook secret, works from any CRM or website without CORS errors, and no longer rejects a lead for being sent twice.

API & Webhook Trigger — Developer API Key Authentication

The API/Webhook trigger node in the workflow builder now uses Developer API keys for authentication, offering enhanced security and flexibility. This update resolves previous CORS issues, allowing seamless integration with any CRM or website, and ensures that retried or duplicate lead submissions are no longer rejected.

How It Works

This feature allows you to initiate campaign workflows by sending data via an API or webhook from external systems like your CRM, website, or ad platform. Instead of a unique secret for each campaign, you'll use a globally managed Developer API key for authentication. When a POST request is made to the webhook URL with a valid API key, the system processes the lead and initiates the associated workflow, even if the lead has been sent previously.

How to Use

  1. Open a campaign's Workflow Builder and add (or select) the API / Webhook trigger node.
  2. Copy the node's Webhook URL — this is the endpoint your CRM, website, or ad platform will POST leads to.
  3. Click "Generate API Key" in the node (or go to Developers in settings to create a named key ahead of time).
  4. Copy the key immediately — it's shown only once.
  5. Configure your integration to POST leads to the webhook URL with header Authorization: Api-Key <your-key>.
  6. Map incoming payload fields to contact properties using the node's Parameter Mapping section.

Benefits

  • Works from any CRM or website: A CORS issue that blocked browser-side integrations from calling the webhook directly is fixed.
  • Enhanced Security and Management: Keys are named, listed, and individually revocable from Developer Settings instead of one hidden per-campaign secret.
  • Flexible Key Management: Multiple keys can be active at once, so generating a new one never breaks an integration already using an older key.
  • Improved Lead Processing: Retried or duplicate sends from a CRM no longer get rejected as "duplicate" — every valid POST enters the workflow.
  • Streamlined Integration: The endpoint URL is also shorter, and the same webhook now works correctly for standard (non-workflow) campaigns too.

This feature is closely related to Developer API Keys, the Campaign Workflow Builder, and Standard Campaign audience sources.