There's no native Zapier app for Run a Call today. You can still connect to Zapier — and any other automation platform — using the REST API and webhooks.

Note

A native Zapier app is on the roadmap. Today, you wire it up with raw Webhooks by Zapier + REST API calls.

How to connect via API + webhooks

For most Zapier scenarios:

DirectionMethod
Triggers (Run a Call → Zapier)Webhook subscriptions. Subscribe to events like job.completed or invoice.paid; Zapier listens on a webhook URL.
Actions (Zapier → Run a Call)REST API. Zapier's Webhooks by Zapier app can POST to your /api/v1/... endpoints with your API key.

See Subscribing to webhooks and REST API overview.

A typical Zap pattern

"When a job is completed in Run a Call, add the customer to a Mailchimp list."

  1. Zap trigger — Webhooks by Zapier → Catch Hook.
  2. In Run a Call, subscribe to job.completed events, posting to the Zapier webhook URL.
  3. Zap step 2 — Mailchimp → Add Subscriber to Tag, with the customer's email from the Run a Call payload.

The same pattern works for any platform Zapier supports (HubSpot, Pipedrive, Slack, Notion, etc.).

A typical reverse pattern

"When a Mailchimp campaign is sent, add a note to all targeted customers in Run a Call."

  1. Zap trigger — Mailchimp event.
  2. Zap step 2 — Webhooks by Zapier → POST to https://app.runacall.com/api/v1/customers/{id}/notes with your API key in the Authorization header.

Limitations of the no-native-app approach

LimitationDetail
No pre-built triggers / actionsYou build each step with raw Webhooks / API calls
Field mapping is manualYou decide what to send and what to map
Auth setup is per-ZapYou can't share an API key across many Zaps with one click

For shops with many integrations, this gets cumbersome.

Make / n8n / others

Same approach — use webhooks for triggers and HTTP requests with API keys for actions. The REST API is platform-neutral.