What are webhooks and what can they do
Webhooks let you send your social data — posts, reactions, comments, contacts, job changes, and AI Agent outputs — to any external system in real time. If you can accept an HTTP POST request, you can receive data from your Signals.
Written By Kevin Lawrie
Last updated About 24 hours ago
The core idea
Every time your Signal runs and finds something new, a webhook can instantly push that data to a URL you control. Your CRM, your data warehouse, your custom app, your automation platform — anything that can receive a JSON payload over HTTPS can be a webhook destination.
Unlike the built-in integrations (HubSpot, Instantly, Smartlead, etc.) which push contacts in a structured way to specific platforms, webhooks are open-ended. You decide what happens with the data on the receiving end.
What can be sent via webhook
Webhooks can carry every type of data your Signals produce:
How webhooks work
Webhooks accept any valid HTTPS endpoint. The platform sends structured JSON payloads via HTTP POST to the URL you provide. Use them for custom apps, automation platforms (Make, Zapier, n8n), data warehouses, CRMs, or any system that can receive an HTTP request — including Clay.
Where webhooks fit in the platform
Webhooks are created once in Integrations → Webhooks and then assigned wherever you need them:
Signal Configure step — assign a webhook to receive posts, reactions, comments, contacts, or job changes as the Signal runs
Contacts manager — manually push selected contacts to a webhook
AI Agent actions — fire a webhook when an agent's conditional rule is triggered, with the AI's output included in the payload
Failure handling
If a webhook endpoint returns an error or is unreachable, the platform retries delivery. After 3 consecutive failures, the webhook is automatically disabled and you receive an alert email. Re-enable it from Integrations → Webhooks once your endpoint is back up.
All webhooks require HTTPS endpoints.