Zapier integration support and beta status
RadiusOS is live in the Zapier App Directory as a public beta integration. This article covers where to get help when a Zap behaves unexpectedly, what beta status means, and how to report a bug so it lands in front of the right team.
How RadiusOS works with Zapier
RadiusOS exposes 5 triggers (contact created, contact updated, stage changed, task created, task completed) and 3 actions (create contact, create task, move stage) in Zapier. You connect once with a workspace-scoped API key from Settings -> API Keys, and every Zap you build reads from or writes to that workspace.
For the full setup walkthrough, see the canonical guide at /help/zapier. For pre-built workflow ideas, see /help/zapier-recipes.
Where to get help with a Zap
Two paths, depending on which side of the Zap is misbehaving.
| What's wrong | Where to ask |
|---|---|
| RadiusOS isn't sending or receiving data (API key rejected, Move Stage action errors, contact missing from the dropdown picker, trigger doesn't fire on a real event in RadiusOS) | Email support@radiusos.ai with the Zap URL, the timestamp, and the error message. We have direct access to the logs. |
| The Zap itself is misbehaving (Zap stuck, task quota exhausted, the other app isn't connecting, scheduling delays, account-level connection issues) | Open a ticket at https://zapier.com/app/get-help. Zapier's support team handles their own platform issues end-to-end. |
When in doubt, ask both. We'd rather see a duplicate ticket than have an issue go to the wrong team and sit untouched.
Beta status: what it means for you
RadiusOS is in Zapier's 90-day Beta phase. In practice this means: anyone with a Zapier account can find RadiusOS by name and connect, and the integration works exactly the same as a fully-promoted app. The only practical difference is that if Zapier sees a spike in support tickets, they reserve the right to revert the listing to Private while issues get addressed. After 90 days of healthy operation we auto-enter the Zapier Partner Program.
You don't need to do anything special during the beta phase. Your Zaps will keep running. We'll update this article when we exit beta.
Reporting a bug
Two places, depending on which side of the Zap the bug is on. If it's a RadiusOS-side bug (the API returned an error, the data RadiusOS sent looks wrong, a field is missing from the action picker), the fastest path is the in-product feedback widget (the small icon in the bottom-right of every workspace page) or an email to support@radiusos.ai.
If it's a Zap-side bug (the Zap is stuck, retries aren't working, the schedule is delayed), report to Zapier at https://zapier.com/app/get-help. Those reports show up in our partner dashboard's Bug & Feature Requests section automatically, so we see them too.