Configure webhooks
Receive real-time notifications for every Metrikia event. Complete setup guide with Zapier, Make, and n8n examples.
What is a webhook and why use one?
A webhook is an HTTP notification automatically sent by Metrikia when an event occurs. Instead of regularly checking your data (polling), you receive information in real time, as soon as a lead is created, a deal is won, or a sync completes.
Typical use cases:
- Receive a Slack notification when a deal is won
- Automatically create a calendar event when a lead is qualified
- Sync Metrikia leads with a CRM not natively supported
- Trigger a welcome email when a new lead arrives
- Feed your BI tool in real time
Available events
| Event | Trigger | Typical use |
|---|---|---|
| lead.created | A new lead is created in the CRM | Team notification, external CRM sync |
| lead.status_changed | A lead status changes | Workflow automation, qualification alerts |
| deal.created | A new deal is created | Pipeline update, manager alert |
| deal.won | A deal is marked as won | Celebration notification, invoicing |
| deal.lost | A deal is marked as lost | Loss analysis, follow-up tracking |
| sync.completed | An ADS sync completes | BI refresh, data verification |
| sync.failed | An ADS sync fails | Ops alert, diagnostics |
Step-by-step configuration
1. Create a receiving endpoint
Your server (or a third-party service like Zapier, Make, n8n) must expose an HTTP(S) endpoint that accepts POST requests.
Example URL: POST https://your-server.com/webhooks/metrikia
The endpoint must:
- Accept
Content-Type: application/json - Return a 200 code within 10 seconds
- Validate the HMAC signature (strongly recommended for security)
2. Register the webhook in Metrikia
- Go to Settings > Integrations > Webhooks
- Click + New webhook
- URL: your endpoint address
- Events: check the events you want to receive
- Secret: enter a secret for HMAC validation (32 characters minimum recommended)
- Click Save
3. Test your webhook
Click the Test button next to your webhook. Metrikia sends a test event to your endpoint. Check your logs to verify data is received correctly.
Pro tip: Use a service like webhook.site or RequestBin to test your webhook before configuring it on your production server.
Payload structure
Each webhook sends a JSON with the following structure:
event: event type (e.g., "lead.created")timestamp: ISO 8601 date/time (e.g., "2026-03-12T14:30:00Z")data: event data (varies by type)
lead.created payload
The data object contains: id, firstName, lastName, email, phone, status, source, createdAt, assignedTo.
deal.won payload
The data object contains: id, title, amount, currency, leadId, leadName, source, closedAt, dealLines.
Security: HMAC validation
Each request includes an X-Webhook-Signature header containing the HMAC-SHA256 signature of the body using your secret.
To validate server-side:
- Get the raw (unparsed) body of the request
- Compute the HMAC-SHA256 with your secret
- Compare the result with the
X-Webhook-Signatureheader - Reject the request if the signature does not match
Security best practices:
- Always use HTTPS: never configure a webhook over unencrypted HTTP
- Always validate HMAC: a webhook without validation can receive fraudulent requests
- Respond quickly: return 200 in less than 10 seconds, process content asynchronously
- Handle duplicates: the same event may be sent multiple times on timeout, implement idempotency
- Log everything: keep a record of received webhooks for easier debugging
No-code integrations
Zapier
- Create a new Zap with the "Webhooks by Zapier" > "Catch Hook" trigger
- Copy the Zapier webhook URL
- Configure this URL in Metrikia (Settings > Webhooks)
- Test the send from Metrikia
- Add desired actions in Zapier (Slack, Email, Google Sheets, etc.)
Make (formerly Integromat)
- Create a new scenario with the "Webhooks" > "Custom webhook" module
- Copy the URL provided by Make
- Configure this URL in Metrikia
- Make will automatically detect the data structure on first send
- Add action modules (CRM, Slack, Email, etc.)
n8n
- Create a new workflow with the "Webhook" node
- Configure the path and POST method
- Copy the complete n8n webhook URL
- Configure this URL in Metrikia
- Add processing and action nodes
Troubleshooting
I am not receiving webhooks:
- Verify your endpoint is publicly accessible (not behind a VPN or firewall)
- Test the URL with a tool like curl from outside
- Check send logs in Settings > Webhooks > History
Webhooks are arriving late:
- A few seconds delay under load is normal
- If delay exceeds 1 minute, check the Metrikia Status page
- Verify your endpoint responds in under 10 seconds
401/403 errors:
- Your endpoint may require HTTP authentication
- Metrikia does not send authentication credentials, use HMAC instead
- Check your WAF or firewall rules
Webhook automatically disabled:
- After 10 consecutive failures, Metrikia automatically disables the webhook
- Fix the server-side issue and re-enable the webhook in Settings
Previous guide
Advanced API integration
Next guide
Multi-touch attribution: understanding and choosing the right model
To go further, check out our blog, the documentation or contact support.