Webhook Integration
Send the data you capture through Bridged straight into your own systems - the moment a visitor submits a form.
What it does
A webhook is a live connection between a Bridged CTA and an external endpoint. When a visitor submits a form, Bridged instantly sends (POSTs) that submission to a URL you control - your CRM, registration platform, marketing automation tool, or any internal service.
You set up the connection once, then reuse it across as many CTAs and agents as you like. No engineering support, no CSV exports, no delay.
When to use it
Reach for a webhook whenever a form submission needs to go somewhere automatically:
Push leads into your CRM as they're captured, already mapped to the right fields.
Register attendees directly in your event or ticketing platform.
Trigger downstream automations - welcome emails, Slack alerts, enrichment workflows.
Feed a custom internal system that expects data in a specific shape.
If you're currently exporting leads and re-uploading them elsewhere, a webhook removes that step entirely.
How it works
Every webhook defines two things: where data goes (the endpoint) and what data is sent (the payload fields).
Payload fields come in two types, and the distinction matters:
Field type | Where it's filled | Example |
|---|---|---|
Form field | Becomes a visible input on the CTA that the visitor fills in |
|
Non-form field | Hidden from visitors; you set the value in the Agent Wizard using a static value or data pulled from elsewhere |
|
This lets a single form collect what the visitor sees and attach behind-the-scenes context your endpoint needs - without cluttering the form.
Step 1 - Create the webhook
Go to Settings → Integrations → Webhooks and click Create Webhook. The setup runs through three steps.
1. Configuration
Webhook Name - how you'll recognise it later (e.g. Prod Test #1).
Description - optional notes, handy for whoever maintains the integration.
Endpoint URL - where submissions are sent.
2. Payload & Headers
Request Headers - add any headers your endpoint requires.
Content-Type: application/jsonis included by default.Payload Fields - define each field the webhook expects. For every field, choose Form Field or Non Form Field. The counter at the bottom keeps a running tally of each type.
3. Test & Settings
Send a mock payload to your endpoint and confirm it's reachable before going live. You'll see a preview of the exact POST request, with form fields shown as <user_input> placeholders. When it checks out, click Create.
Step 2 - Attach the webhook to a CTA
Open a CTA in Screens → CTA and go to the Design step. Toggle on Webhook integration and pick your webhook from the Select webhook dropdown.
Bridged automatically pulls in the webhook's form fields as inputs on the CTA - Email, First Name, Last Name, and so on - so the form always matches what your endpoint expects.
Non-form fields don't appear here. They're configured in the Agent Wizard (next step).
Step 3 - Configure non-form fields in the Agent Wizard
When you create or edit an agent that uses this CTA, the Design step shows a Webhook section listing every non-form field. For each one, set how it's populated:
Static Value - a fixed value sent with every submission (e.g.
editionId = 7621,gateUrl = google.com).Dynamic sources - pull the value from elsewhere, such as another CTA, user questions, or a poll answer.
This is where you enrich each submission with context the visitor never sees, so your endpoint receives a complete, correctly shaped payload every time.
Putting it together
Create the webhook once in Settings → Integrations.
Attach it to any CTA - form fields appear automatically.
Map non-form fields in the Agent Wizard.
On submit, Bridged sends the full payload to your endpoint in real time.
Set it up once, reuse it everywhere.