Home Integrations Webhooks in and out

Webhooks in and out

Last updated on Sep 29, 2026

Webhooks connect PowerDialer to systems that have no built-in integration. Both kinds are managed from the contact list screen.

Inbound webhooks — receiving contacts

An inbound webhook gives you a URL. Anything that can POST JSON — a form, a lead vendor, Zapier, your own backend — can push contacts into a list.

Setting one up

  1. Create Webhook. Give it a name and an optional description.
  2. Optionally tick Create new list every day, which files each day's arrivals into its own dated list. Useful when you work leads by the day they landed.
  3. Copy Webhook URL and give it to the sending system.
  4. Send a test payload first. The app is explicit about this: "Before configuring field mappings, you need to send a test webhook request." It gives you a ready-made curl command to copy.
  5. Refresh, then map the fields from your sample payload onto PowerDialer's contact fields — the same fields as a CSV import.

You cannot map fields you have never sent, which is why the test payload comes first. Send a sample that includes every field you will ever send, not just the required ones.

Outbound webhooks — pushing events

An outbound webhook posts to a URL you own when something happens in PowerDialer.

Setting one up

  1. Create Outbound Webhook — name, URL, description, payload format (JSON or form data), and any headers you need, such as an Authorization header.
  2. Add one or more triggers: pick the event type, and optionally add event filters so only some events fire.
  3. Check delivery history to see what was sent and what came back.

Triggers and filters are how you avoid drowning your endpoint. A webhook on every call event from a team of ten at three parallel lines is a lot of traffic; a webhook filtered to Meeting Booked is a handful a day and is actually useful.

Practical notes

Return a 2xx quickly. Do the work asynchronously on your side; a slow endpoint looks like a failed delivery.

Expect repeats. Build your receiver so processing the same event twice is harmless.

Protect the inbound URL. Anyone holding it can write contacts into your account. Treat it like a credential — do not paste it into a shared document or a public repository.

Watch delivery history after any change on your side. A deploy that changes an endpoint's response will silently stop the flow otherwise.