Skip to Content
GuidesData pipesConnectorsWebhook

Webhook

The webhook pipe is the catch-all connector: if a system can send or receive an HTTPS request, you can pipe it. Use it when there’s no purpose-built connector for your tool.

DirectionWhat it does
Inbound (your system → Active Reach)Your app POSTs events (signups, purchases, custom actions) to an Active Reach URL.
Outbound (Active Reach → your system)Active Reach POSTs events to your endpoint as they happen.

Inbound webhook

Create the pipe

Go to Settings → Data Pipes → New pipe → Webhook → Inbound. Active Reach gives you a unique URL and a signing secret.

Send events

POST JSON to the URL. Include the contact identity (phone or email) and the event name plus any properties:

{
  "event": "purchase_completed",
  "phone": "+919876543210",
  "properties": { "amount": 1499, "currency": "INR", "sku": "PLAN-PRO" }
}

Map fields

In the wizard, map the JSON fields to contact traits or event properties.

Verify the signature

Active Reach signs nothing on inbound — instead you sign your payload with the shared secret (HMAC-SHA256) and Active Reach verifies it, so spoofed events are rejected.

Outbound webhook

Choose which events Active Reach should forward and the destination URL. Each delivery is signed so your endpoint can verify it came from Active Reach. Failed deliveries are retried with backoff; persistent failures surface on the pipe’s sync health.

Use HTTPS endpoints only, and always verify the signature on the receiving side. Treat the signing secret like a password.

TelegramBigQuery