Connect RadiusOS to 6,000+ apps with Zapier
Zapier connects RadiusOS to apps like Typeform, Calendly, Stripe, Gmail, Slack, Google Sheets, and thousands of others. Use it to push new leads from a web form into your CRM, kick off a follow-up task when a payment lands, or post a Slack note when a deal moves to Won.
How it works
Zapier is a third-party service that wires apps together with no-code workflows called Zaps. Each Zap has a trigger (an event in one app) and one or more actions (things that happen in other apps). RadiusOS shows up in Zapier as both a trigger source (when a new contact arrives, when a stage changes) and an action target (create a contact, create a task, move a stage).
You connect Zapier to RadiusOS once using an API key from your account. After that, every Zap you build can read from or write to your workspace.
Zapier is included on every plan. Free includes 1 active Zap. Pro, Business, and Team include unlimited Zaps.
Connect Zapier to RadiusOS
Create an API key in RadiusOS
Go to Settings -> API Keys and click New API Key. Give it a name like 'Zapier' so you can recognize it later. Copy the key once it appears (we only show it once for security).
Open Zapier and find RadiusOS
Sign in to zapier.com and search the app directory for RadiusOS. Click Connect.
Paste your API key
Zapier will ask for your API key. Paste the value you copied. Zapier will validate the key against RadiusOS and label the connection with your workspace name.
Build your first Zap
Pick a trigger app (like Typeform or Calendly) and an action in RadiusOS (like Create Contact). Test it once, turn it on, and the Zap runs every time the trigger fires.
What you can wire up
| Direction | What's available |
|---|---|
| Triggers (RadiusOS -> Zapier) | Customer level: new contact, contact updated, stage moved, task created, task completed. Job level: quote approved, job status changed, visit completed, invoice sent, invoice paid |
| Actions (Zapier -> RadiusOS) | Create contact, create task, move pipeline stage |
| Dropdown helpers | Live pickers for pipeline stages and contacts so Zapier shows real options, not text fields |
See the recipe library for ready-made Zaps you can copy.
Common workflows by industry
Three concrete Zaps that map to the kinds of work RadiusOS users actually run. Use these as starting points; the recipe library at /help/zapier-recipes covers eight more.
Trades & home services - quote-to-paid loop
Trigger 1: Calendly booking (estimate visit) -> Action: Create Contact in RadiusOS. Trigger 2: Stage moved to 'Estimate Sent' -> Action: Create Task in RadiusOS due in 3 days ('Follow up on estimate'). Trigger 3: Stripe payment received -> Action: Move Pipeline Stage in RadiusOS to 'Paid'. The loop runs without you remembering to update the CRM after every job.
Realtors - showing-to-listing pipeline
Trigger 1: Typeform 'Schedule a showing' -> Action: Create Contact in RadiusOS, tagged 'showing'. Trigger 2: Stage moved to 'Offer' -> Action: Send Channel Message in Slack ('New offer on $address'). Trigger 3: Task completed -> Action: Create Spreadsheet Row in Google Sheets to track time-to-close. Keeps your team in the loop without breaking your phone-and-spreadsheet workflow.
Solopreneurs & coaches - intake-to-payment
Trigger 1: Tally form submission -> Action: Create Contact in RadiusOS. Trigger 2: New Contact in RadiusOS -> Action: Create Calendly invite. Trigger 3: Stripe charge succeeded -> Action: Move Pipeline Stage in RadiusOS to 'Customer'. From first form fill to paying customer with zero manual data entry.
Frequently asked questions
Do I need a Zapier account separate from my RadiusOS account?
Yes. Zapier is a third-party service. You sign up at zapier.com and connect to RadiusOS using your RadiusOS API key. Zapier's free tier includes 100 tasks per month across all your Zaps - usually enough for a small business running 1-2 Zaps.
What's the difference between a Zap and an automation in RadiusOS?
RadiusOS automations run inside RadiusOS only - move stages, create tasks, send emails. Zaps run between RadiusOS and other apps (Typeform, Stripe, Slack, etc.). If your workflow stays inside RadiusOS, use an automation; if it crosses apps, use a Zap.
Why can't I see my contact in the Zapier 'contact picker' dropdown?
The picker shows the 25 most recently active contacts by default. To find an older contact, type part of the name or email into the dropdown - it searches the full workspace. If a contact still isn't showing, confirm it's in the same workspace as the API key you connected.
What happens if the same person comes through a Zap twice?
You get one customer, not two. Before Create Contact makes a record it looks for someone you already have: the same email address, the same phone number (compared as digits, so formatting doesn't matter), or the same name at the same address. On a match it updates that person with whatever the Zap sent and returns them with matched set to true, so a form that fires twice or a Zap you re-run is harmless. It only fills in fields the Zap actually sent, so it can't blank out a detail you typed in by hand. It will never merge two people on name alone - two different Dave Smiths stay two customers.
Can I use Zapier with the free RadiusOS plan?
Yes. Free includes 1 active Zap. That's enough for the highest-leverage workflow most users have - usually 'lead form -> RadiusOS contact'. Pro and above remove the limit.
Tier limits
| Plan | Active Zaps |
|---|---|
| Free | 1 |
| Pro | Unlimited |
| Business | Unlimited |
| Team | Unlimited |
An 'active' Zap is one that is turned on inside Zapier. Zaps that are paused or in draft do not count against the limit. If you hit your limit, you'll see a 'plan limit reached' error in Zapier when you try to turn on a new Zap; upgrade in Settings -> Billing or pause an existing Zap.
Security and revocation
API keys are scoped to a single workspace. They cannot read or write data outside that workspace. If you want to revoke Zapier's access, revoke the API key under Settings -> API Keys; every Zap connected with that key stops working immediately, and the Zap will report that the key was revoked rather than that it was wrong.
A revoked key stays on the list, greyed out, showing the date it was stopped. That is deliberate: a key that simply vanished could not tell you later whether it had been revoked or had never existed, and those are different answers when somebody asks why an integration broke.
You can also give a key an end date when you create it - 30, 60 or 90 days, or a year. The default is no end date, so every key made before this existed keeps working. Pick one when the key is for a contractor, a trial, or anything you would rather not have to remember to turn off.
Use a separate API key for each integration (one for Zapier, one for Claude Desktop, one for Cursor, etc.) so you can revoke one without breaking the others.
Building something custom?
The Zapier integration is built on top of a public REST API. If you want to wire RadiusOS into something Zapier doesn't reach (a self-hosted automation runner, an internal tool, a one-off script, n8n, Make.com), you can call the same endpoints directly with the same API key.
The full developer reference lives at /docs/api. It documents every endpoint with auth, request body, response shape, error codes, and a curl example you can copy and paste.