Zapier and Make
RelayOne has apps for Zapier and Make. They let you start a Zap or a scenario the moment something happens in RelayOne, and send WhatsApp messages or update contacts from anything else, without writing code.
Both apps sit on top of the public API and outgoing webhooks and sign in with a RelayOne API key.
Before you start
- Plan. The apps use the public API, so your plan must include API access. Triggers also need outgoing webhooks (Growth and Business). A trigger on a plan without them fails with an "upgrade required" message; actions keep working.
- Webhook allowance. Every Zap that is on with a RelayOne trigger, and every RelayOne webhook in Make, is one webhook endpoint in your account and counts toward your plan's webhook limit. At the limit, turning on another Zap fails. Turn off Zaps you no longer use, or delete unused endpoints.
- Role. Only admins and owners can create API keys.
Create an API key
Open Settings → API keys → New API key, name it after the integration ("Zapier" or "Make"), and grant only the scopes you need:
| To use | Scope |
|---|---|
| Any trigger (Zapier) or Watch module (Make) | webhooks:manage |
| Send a template message or a text message | messages:send |
| Create or update a contact, add a tag to a contact | contacts:write |
Copy the key when it is shown; RelayOne never shows it again. To rotate it, create a new key, reconnect, then revoke the old one.
Connect
- Zapier: in a Zap, pick RelayOne as the app, choose a trigger or action, and paste the API key when asked to sign in.
- Make: in a scenario, add a RelayOne module, choose Create a connection, and paste the API key.
Triggers
Triggers are instant. Zapier calls them triggers; Make calls them Watch modules.
| Trigger | Fires when |
|---|---|
| New inbound message | A contact sends you a WhatsApp message |
| New contact | A contact is created, from any source |
| Updated contact | A contact's phone, name, email, company, avatar or owner changes |
| Tag added to contact | A tag is added to a contact |
| Deal stage changed | A deal moves to a different pipeline stage |
| New order | A contact places an order from your WhatsApp catalog |
| Order paid | An order is paid through its payment link |
| Conversation closed | A conversation is closed |
Messages and orders arrive immediately. Contact, tag, deal and conversation events arrive within about a minute of the change. While you set a trigger up, the test shows a fixed example, not data from your account.
Actions
| Action | What it does |
|---|---|
| Send template message | Sends an approved WhatsApp template with its variables. Works at any time. |
| Send text message | Sends free-form text. WhatsApp delivers it only within 24 hours of the contact's last message to you; outside that window, send a template. |
| Create or update contact | Creates the contact with that phone number, or updates the existing one with the fields you filled in. Empty fields are left alone. |
| Add tag to contact | Adds a tag to the contact with that phone number, keeping its other tags. Creates the contact and the tag if needed. |
Both send actions have a From number dropdown listing your connected WhatsApp numbers; leave it empty to use your default number.
What you will see in RelayOne
Each Zap trigger that is on, and each RelayOne webhook in Make, shows up in Settings → Webhooks as an endpoint with a Zapier or Make address. Its Deliveries log lists every attempt, and you can Redeliver one, like any other endpoint.
Manage these from Zapier or Make, not from RelayOne:
- Turning a Zap off (or deleting the Make webhook) removes the endpoint. Deleting it in RelayOne instead leaves the Zap on but deaf; turn the Zap off and on again.
- Regenerating the endpoint's signing secret in RelayOne makes the Zapier trigger refuse deliveries until you turn the Zap off and on again.
- After a run of failed deliveries RelayOne disables the endpoint. Re-enable it in Settings → Webhooks, or turn the Zap off and on.
Troubleshooting
| Message | Cause | Fix |
|---|---|---|
| "Rejected the API key" | The key was revoked, expired, or mistyped | Reconnect with a new key |
| "This API key is missing the scope" | The key lacks a scope this step needs | Create a key with the scopes above and reconnect |
| "Upgrade required" for webhooks | Your plan doesn't include outgoing webhooks | Upgrade to use triggers |
| "Upgrade required" for the webhook limit | Every webhook endpoint your plan allows is in use | Turn off unused Zaps, delete unused endpoints, or upgrade |
| A text message fails in the inbox | It was sent more than 24 hours after the contact's last message | Use Send template message |
| "Too many requests" | More than 120 requests a minute with one key | Zapier and Make retry automatically |
For the technical details, including the request and payload formats other platforms can use, see Developers and the API.