Zapier · Make · n8n

Connect Run Wild to whatever runs your stack.

No two service businesses run the same stack. Some pipe everything through Zapier. Some operate on Make. Some self-host n8n. Some have a developer who wants webhooks and an API.

Run Wild meets every shop where it is. Trigger workflows on any conversation event. Push data into the systems you already use. Replace the brittle CSV exports and manual handoffs with reliable automation.

Start Selling

No credit card required.

See how it works

How it works

Real-time hooks into your operations.

Pick your platform

Zapier, Make, or n8n (self-hosted or cloud) over signed webhooks. Or call our REST API directly.

Subscribe to events

New lead, stage change, booking confirmed, payment received, conversation handed off. Fine-grained event types.

Route data anywhere

Trigger workflows, sync to spreadsheets, fire Slack notifications, update other CRMs, or kick off field-service jobs (e.g. ServiceTitan).

Bring data back in

Action endpoints let external systems push back. New contact, stage update, conversation note — all programmatic.

What you get

Open platform, real-time hooks.

Zapier-ready

Connect Run Wild to Zapier through signed webhooks and the REST API. 6,000+ apps within reach.

Make scenarios

Complex multi-step automations with branching, parallel paths, and aggregations.

n8n self-hosted

For shops that want their automation infrastructure inside their own cloud.

Webhooks on every event

Subscribe to lead, stage, booking, payment, and conversation events. Signed payloads, retry semantics.

Sub-second delivery

Events fire within 200ms of the trigger. No batch jobs, no polling.

Bidirectional sync

External writes push back into Run Wild. Contacts, stages, notes, and tags stay aligned.

Recipe-ready events

Wire up common patterns in a few steps — e.g. "New booking → Slack notification" or "Paid deposit → QuickBooks invoice."

Questions about automation.

Which platforms can I connect?

Zapier, Make, and n8n all connect through signed webhooks and the REST API with a full event schema — as does any tool that can consume a webhook or call a REST endpoint.

Are webhooks reliable?

Yes. Webhooks are signed, retried with exponential backoff up to 24 hours, and observable in-product. You see what fired, what was received, and what failed.

Can I trigger Run Wild actions from outside?

Yes. The REST API lets external systems write to Run Wild — create contacts, advance stages, send messages, attach notes — so any platform that can call an endpoint can drive actions.

What about rate limits?

Generous by default — 100 requests/second on most tiers. Enterprise customers get dedicated capacity.

Related capabilities