Configure webhooks | Guides | Metrikia
Advanced3 min

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

EventTriggerTypical use
lead.createdA new lead is created in the CRMTeam notification, external CRM sync
lead.status_changedA lead status changesWorkflow automation, qualification alerts
deal.createdA new deal is createdPipeline update, manager alert
deal.wonA deal is marked as wonCelebration notification, invoicing
deal.lostA deal is marked as lostLoss analysis, follow-up tracking
sync.completedAn ADS sync completesBI refresh, data verification
sync.failedAn ADS sync failsOps 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

  1. Go to Settings > Integrations > Webhooks
  2. Click + New webhook
  3. URL: your endpoint address
  4. Events: check the events you want to receive
  5. Secret: enter a secret for HMAC validation (32 characters minimum recommended)
  6. 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:

  1. Get the raw (unparsed) body of the request
  2. Compute the HMAC-SHA256 with your secret
  3. Compare the result with the X-Webhook-Signature header
  4. 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

  1. Create a new Zap with the "Webhooks by Zapier" > "Catch Hook" trigger
  2. Copy the Zapier webhook URL
  3. Configure this URL in Metrikia (Settings > Webhooks)
  4. Test the send from Metrikia
  5. Add desired actions in Zapier (Slack, Email, Google Sheets, etc.)

Make (formerly Integromat)

  1. Create a new scenario with the "Webhooks" > "Custom webhook" module
  2. Copy the URL provided by Make
  3. Configure this URL in Metrikia
  4. Make will automatically detect the data structure on first send
  5. Add action modules (CRM, Slack, Email, etc.)

n8n

  1. Create a new workflow with the "Webhook" node
  2. Configure the path and POST method
  3. Copy the complete n8n webhook URL
  4. Configure this URL in Metrikia
  5. 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

To go further, check out our blog, the documentation or contact support.

Ready to take action?

Create your Metrikia account and apply this guide in minutes.