🔗 Webhook Trigger

Overview

The Webhook Trigger starts your workflow when an HTTP request is received at a unique URL. Use it to connect external systems, third-party services, or custom applications to your Falcon Builder workflows.

Configuration

• Webhook Path — auto-generated unique path for your workflow
• HTTP Method — POST (default). The webhook URL accepts POST requests with JSON body.
• Authentication — optional authentication to secure your webhook endpoint
• Deduplication Key — optional path to a unique event ID in the payload (e.g. update_id, message.sid)

Event Deduplication

Providers like Meta, Telegram, and Twilio deliver webhooks at least once — a slow or failed acknowledgement makes them redeliver the same event. Set a Deduplication Key to make retried deliveries safe:

• The key names a payload field that uniquely identifies the event — dot notation for nested fields (e.g. update_id for Telegram, entry.0.id for Meta, MessageSid for Twilio)
• The first delivery claims the key and runs the workflow. Redeliveries with an already-seen value are acknowledged with 200 and { "duplicate": true } — no second execution, no double-processing
• Claims are checked before the execution is created, so even two simultaneous retries can't both run — the database enforces uniqueness
• Applies to the Production URL only — Test URL requests always run, so you can replay a payload from the editor. Claims expire after 72 hours.
• WhatsApp/SMS triggers deduplicate automatically on Twilio's MessageSid — no configuration needed

How It Works

• Add a Webhook Trigger node to your workflow and save — a unique URL is generated
• Copy the webhook URL and configure your external system to send POST requests to it
• The request body is available as {{$json}} in downstream nodes
• Use the Respond to Webhook node to send a custom HTTP response back to the caller

Accessing Webhook Data

• {{$json.fieldName}} — access any field from the POST body
• {{$json.nested.field}} — access nested JSON properties
• {{$json.items[0].name}} — access array elements

Common Use Cases

• Lead capture from forms — receive form submissions from your website, landing pages, or Typeform and route them through AI scoring and CRM sync
• Payment notifications — listen for Stripe webhook events to trigger order processing, email confirmations, or database updates
• CI/CD pipeline triggers — start deployment or notification workflows when GitHub or GitLab push events fire
• IoT and device events — ingest sensor data or device alerts and trigger multi-step analysis and notification workflows