Skip to main content

Webhooks

Webhooks in Conversion

Updated this week

Webhooks let you connect Conversion workflows to almost any external tool by sending real-time data out whenever a workflow runs. You can use them to push enriched contact data to Zapier, route information into a custom internal system, or trigger follow-up actions in tools that don’t have native integrations.



Setting up webhooks in settings

To set one up, go to Settings → Integrations. Under Webhooks, click Add webhook. You’ll be asked to enter:

  • Webhook URL: the endpoint where Conversion will send the data

  • Bearer token (optional): adds a layer of authentication so only authorized requests go through

After entering the details, click Continue and then Save. Your webhook will appear in the integrations list. You can edit it at any time by updating the URL, token, or request body. There’s also a Test webhook button to send a sample payload and confirm the connection works before you start using it in live workflows.



Using webhooks in workflows

Once saved, you can use a webhook in any workflow by dragging in the Webhook action block. From there, select the webhook you created. Whenever that step runs, Conversion will send the event payload directly to your configured URL, including any variables you’ve mapped in the workflow.

Webhooks require at least one variable to be sent. If a contact does not have any variables that match, Conversion will skip enrichment for that record and the webhook will not fire. This prevents empty or incomplete payloads from being pushed into your connected systems.



Best practices

  • Use bearer tokens whenever possible to secure your requests

  • Test each webhook with sample data before activating a workflow

  • Combine webhooks with Magic Enrich to pass richer contact data into your external systems

Did this answer your question?