ZoeRelay
Integration guide

Connect ZoeRelay to Zapier

Use customer and support events to start Zaps, or let Zaps update the support workspace your team already uses.

Before you start

The ZoeRelay Zapier integration is currently available by private invitation. Ask your ZoeRelay workspace administrator for access. You need a ZoeRelay account with access to the workspace and permissions for each event or action you plan to use. A Zap connection belongs to one selected workspace; use a separate connection for another workspace.

Connect your account

  1. Accept the private Zapier invitation and open the Zap editor.
  2. Choose ZoeRelay as the trigger or action app, then select Sign in.
  3. Sign in to ZoeRelay if prompted. Review the requested access, select the correct workspace and choose Allow.
  4. Return to Zapier and test the connection. The account test reads your workspace identity.

ZoeRelay uses OAuth 2.0. Never paste an access token, password or consent proof into a Zap field. If the workspace is missing, ask its owner to confirm your membership. If you change workspaces, add a new Zapier connection for the new workspace.

Triggers

Choose from New Contact, Contact Updated, New Conversation, New Incoming Message, Conversation Closed, New Ticket, Ticket Updated, Human Handoff Requested, Tag Added, CSAT Response Submitted, and Automation Run Completed. Each trigger subscribes to a ZoeRelay REST Hook. Use a harmless downstream step when testing a trigger; avoid sending test messages to real customers.

Actions

Create Contact, Update Contact, Create Ticket, Update Ticket, Create Conversation, Send Message, Add Internal Note, Assign Conversation, Update Conversation Status, Add Tag, Remove Tag, Request Human Handoff, and Run Automation can change workspace data. Check the selected record and recipients before enabling a Zap. The automation must be active and enabled for Zapier invocation. Do not run an automation from its own completion trigger.

Searches and Find or Create

Find Contact searches by email, phone or selected contact. Find Ticket searches by ticket or contact email. Find Conversation searches by conversation, contact email or external reference. Find or Create Contact uses the contact search first and creates a contact only when no match exists. Use a stable email or phone to avoid duplicate contacts. Zapier also uses hidden lookup helpers for users, tags, inboxes and automations in dropdowns.

Example Zaps

For a multi-step Zap, pass IDs from an earlier step into later fields and confirm all steps use the same ZoeRelay workspace connection. Use a filter before actions that could create loops or send customer-facing content.

Repeated actions and retries

Each action has an optional Idempotency Key. Map a unique, stable source event ID for every intended action occurrence; reuse that ID when retrying the same occurrence. The default key is based on the action and mapped input values. Therefore two deliberate runs with identical inputs can return the first result instead of performing the action twice during the server's 30-day idempotency window. For repeated identical messages, notes or other writes, map a distinct source event ID. A random value per retry can create duplicates and should be avoided.

Delivery and troubleshooting

REST Hook delivery is asynchronous. A successful subscription enables ZoeRelay to queue matching events; a Zap's run may appear later than the source change. Temporary delivery failures are retried, and a permanently gone hook can be disabled. Check Zap History and the ZoeRelay integration status if an event is missing. A sample shown during setup is only preview data, not proof of a live run.

Disconnect and support

To stop a Zap, turn it off in Zapier. To remove the connection, disconnect ZoeRelay in Zapier or from ZoeRelay Integrations; revocation stops API access and disables its hook subscriptions. Reconnect to create a new authorized connection. For help, use ZoeRelay Support or email [email protected]. Developers can consult the Zapier API reference.