Webhooks

Set up a webhook

This guide takes about five minutes. You need a Professional, Premium or Enterprise plan, or a free trial, and a public HTTPS URL that accepts POST requests. That can be your own app, or a webhook trigger in a tool such as Make or n8n.

1. Open Integrations

In the Jodie app, go to Manual Setup › Integrations. The page has a card for Zapier and a card for Webhooks. Each card shows a status: Connected, Not set up or Needs attention (when an endpoint's latest delivery failed).

Click Manage on the Webhooks card, or go straight to app.heyjodie.com/integrations/webhooks.

The Integrations page in the Jodie app, with a Zapier card and a Webhooks card marked Connected with a Manage button
Integrations has a card for Zapier and a card for Webhooks.

On Basic, the Webhooks card is shown locked with an upgrade prompt. Upgrade to Professional or above to use it.

2. Add an endpoint

Click Add endpoint. In the dialog:

  1. Paste your Endpoint URL. It must start with https://, point to a public host and be no longer than 255 characters.
  2. Under Activity to send, leave All activity selected to receive calls, WhatsApp, email and website chat, plus any kinds of activity added later. Or pick Choose activity and tick only the types you want.
  3. Click Add endpoint.
The Add webhook endpoint dialog with an Endpoint URL field and an Activity to send switch set to All activity
Endpoints receive All activity unless you choose otherwise.

You can add up to 10 endpoints. Each one receives its own copy of every delivery, so you can send the same activity to a CRM and a data warehouse at once.

3. Copy the signing secret

Click an endpoint, or View deliveries, to open its page. The Endpoint card shows its status, what it sends and its Signing secret. Click Show or Copy, and store the secret in your receiver's configuration, for example as a WEBHOOK_SECRET environment variable. Treat it like a password.

An endpoint page showing the endpoint URL, a Send test event button, and the Endpoint card with status Healthy, All activity and a hidden signing secret
Each endpoint has its own signing secret.

Use the secret to verify the Signature header on every request. The Build your receiver card further down the page has example payloads and the same signature code shown in these docs.

4. Send a test event

Click Send test event and pick a kind of activity. Jodie sends sample data straight away, marked with a Test-Event: true header, and opens the delivery so you can see the request and your endpoint's response.

If your endpoint replies with a 2xx status, you're done. Real activity starts arriving the next time a call ends or a conversation closes. If the test fails, the delivery shows what went wrong; see Troubleshooting.

Manage your endpoints

The Webhooks page lists every endpoint with its health, what it sends and how many deliveries it made in the last 7 days.

The Webhooks page listing endpoints, each with a health status, the activity it sends, a Send test event menu, edit and delete buttons and a View deliveries link
Each endpoint shows its health and the activity it receives.
  • Edit (pencil) changes the URL or the activity it receives. The signing secret stays the same.
  • Delete (bin) stops deliveries to that URL and removes its delivery history. This can't be undone.
  • View deliveries opens the delivery log.

The health shown next to each endpoint comes from its latest delivery: Healthy, Failing, Retrying, Sending or No deliveries yet.

Moving from Developers › Webhooks? Webhooks used to live under Developers. The old /developers/webhooks address now redirects to /integrations/webhooks, and existing endpoints, URLs and signing secrets are unchanged. Existing endpoints are set to All activity, so they now also receive email and website chat. Branch on event_type if you only handle calls.

Need a hand?

Our team can help you connect Jodie to your systems.

Email [email protected]