Creating and managing your webhooks

All webhooks are created and managed in one place — Integrations → Webhooks. Once created, a webhook can be assigned to any Signal, used in the Contacts manager, or triggered by an AI Agent.

Written By Kevin Lawrie

Last updated About 23 hours ago

Creating a webhook

  1. Go to Integrations in the left sidebar.

  2. Open the Webhooks tab.

  3. In the Add New Webhook section, enter:

    • Webhook Name — a descriptive label, e.g. "Make.com Automation", "CRM Inbound", "Clay Enrichment"

    • Webhook URL — your HTTPS endpoint URL

  4. Click Add Webhook.

Testing a webhook

Before assigning a webhook to a live Signal, verify it's working by sending a test payload.

From Integrations → Webhooks, each webhook has a Test dropdown with four options:

Test payload What it sends

Send Post Payload Test

A sample LinkedIn post in full production format

Send Contact Payload Test

A sample enriched contact with all 65+ fields

Send Reactions Payload Test

50 sample reactions in batched format

Send Comments Payload Test

50 sample comments in batched format

Check your receiving endpoint after sending a test to confirm the payload arrives and is structured as expected.

Managing existing webhooks

From the Webhooks tab you can:

  • View all webhooks with their name, URL, type badge, and status

  • Edit a webhook name or URL

  • Delete a webhook — this removes it from any Signals or AI Agents it's assigned to

  • Re-enable a disabled webhook (disabled automatically after 3 consecutive delivery failures)

Webhook failure and recovery

If your endpoint returns errors or becomes unreachable, the platform tracks consecutive failures. After 3 failures in a row, the webhook is disabled automatically and you receive an alert email.

To recover:

  1. Fix the issue on your receiving endpoint

  2. Go to Integrations → Webhooks

  3. Re-enable the webhook

  4. Send a test payload to confirm it's working

  5. The webhook will resume delivery on the next Signal run

💡 Tip: Use the test payload feature regularly when making changes to your receiving endpoint — it's the fastest way to catch issues before they affect live data delivery.