There's no Run a Call app to search for inside Zapier. You can still connect Run a Call to thousands of apps through Zapier — or Make, n8n and similar tools — using two building blocks every one of them supports: webhooks (Run a Call tells Zapier something happened) and the REST API (Zapier asks Run a Call to look something up or create a record).

Note

The account owner sets this up, because only the owner can create webhook subscriptions and API keys. It takes about 15 minutes per Zap and a little comfort with copying URLs and JSON field names.

Run a Call → other apps (triggers)

Example: when a job is completed, post a message in Slack.

  1. In Zapier, create a Zap with the trigger Webhooks by Zapier → Catch Hook. Copy the webhook URL Zapier gives you.
  2. In Run a Call, go to Settings → Integrations → Manage subscriptions (Webhooks) and click Create subscription. Paste the Zapier URL into Endpoint URL, give it a Label like Zapier – Slack, tick job.completed, and click Create subscription. (You can skip saving the signing secret for a Zapier-only flow.) See Subscribing to webhooks.
  3. Send a sample. Open the subscription and click Send test event, or complete a real job, then click Test trigger in Zapier so it learns the fields.
  4. Add the action — for example Slack Send Channel Message — and map fields from the event's data.

The Webhook subscriptions page with the Create subscription button highlighted

Useful events for Zaps: customer.created, job.scheduled, job.completed, estimate.approved, invoice.paid, payment.received, call.missed, membership.created. The full list is in Subscribing to webhooks.

Tip

The test event has a different shape from real events (it only says "Hello from Run a Call"). To map real fields, trigger the real event once — create a test customer or complete a job — before setting up the action.

Other apps → Run a Call (actions)

Example: when someone fills out a form on your website, create a customer in Run a Call.

  1. In Run a Call, create an API key with Write access: Settings → Integrations → Manage keys → Create key. Copy it. See Generating API keys.
  2. In Zapier, add an action step Webhooks by Zapier → Custom Request (or POST):
    • Method: POST
    • URL: https://api.runacall.com/v1/customers
    • Headers: Authorization = Bearer <your key> and Content-Type = application/json
    • Data: JSON with the fields to create — for example first_name, last_name, email, phone.
  3. Test the step, then check the new customer in Contacts.

The External REST API keys page with the Create key button highlighted

Tip

Add external_id (for example the form submission ID) and external_source (for example website-form). If the Zap ever runs twice for the same submission, Run a Call updates the existing customer instead of creating a duplicate.

What you can create, update and look up — and the exact field names — is in the API reference. See also the API overview.

Make, n8n and others

Same pattern, different names:

ToolTrigger from Run a CallAction into Run a Call
MakeWebhooks → Custom webhookHTTP → Make a request
n8nWebhook nodeHTTP Request node

Good to know

  • One key per tool. Create a separate API key for Zapier, Make, and so on, so you can revoke one without breaking the others.
  • If a Zap stops firing, check the subscription in Settings → Integrations → Webhooks. After 10 events in a row fail to reach Zapier, it's Auto-paused — fix the Zap, then click Resume.
  • Starting a Run a Call automation from outside? Run a Call automations can also be started by a webhook — see Triggering automations from an inbound webhook.