Skip to main content

​
Connect Zendesk, Jira, Calendly, DocuSign, Slack, Zapier, and n8n

Five of these integrations connect the same way — Zendesk, Jira, Calendly, DocuSign, and Slack each run the same loop: Connect → syncs activate → verify one record → troubleshoot. Zapier and n8n take a different route: you download a per-tenant app definition from Developer → Connectors and authenticate it with your own API key. This page is the numbered runbook for all seven. The endpoint map behind every step below is /api-reference/integrations — this page is the “do this, then this” walkthrough for the same surface.

​
Prerequisites (all seven)

  1. An owner or admin role on your Orbit organization — connect and disconnect are the only tenant-owned controls that touch provider credentials.
  2. An Orbit API key with the integrations:write scope, and integrations:read for the status checks. Connect via API with POST /api/v1/integrations/connect — the dashboard’s Connect button calls the same route.
  3. A working account on the provider side, with one provider-specific prerequisite per section below.
OAuth flows (Zendesk, Jira, Calendly, DocuSign, Slack) open the provider’s consent screen and store the resulting tokens on Orbit’s encrypted connection record. Zapier and n8n skip OAuth entirely — you authenticate the downloaded app with your own dv_live_sk_… API key instead. No step in this page asks you to paste a provider credential into a plain-text field.

​
Zendesk — tickets and end-users into Orbit

What it does end to end. Connecting Zendesk starts two syncs: tickets (Zendesk tickets land on the linked Orbit contact’s timeline) and users (Zendesk end-users import as Orbit contacts). From then on, ticket state and requester history sit next to every messaging channel in the inbox.

​
Step 1 — Connect and authorize

  1. In Orbit, go to Settings → Integrations and find Zendesk.
  2. Click Connect, sign in to Zendesk, and authorize the requested scopes.
  3. Back on the integrations page, Zendesk flips from Not connected to Connected once the token exchange completes.

​
Step 2 — How the data maps

Re-running Connect is safe — re-syncs converge on the same ticket and contact rows, never duplicates.
Create one test ticket in Zendesk with a known requester email, wait for the sync, then open the matching Orbit contact. The ticket should appear on the contact’s timeline and in Customer 360.

​
Step 3 — Troubleshooting

​
Jira — issues linked to conversations

What it does end to end. Connecting Jira starts three syncs: projects, issues, and users. Jira issues then surface inside the Orbit inbox, so an agent can attach the exact issue a customer is asking about to the conversation — and an AI agent can open or update an issue on behalf of a rep.

​
Step 1 — Connect and authorize

  1. Have your Atlassian Cloud site URL ready.
  2. In Orbit, go to Settings → Integrations, find Jira, and click Connect.
  3. Sign in to Atlassian, authorize the requested scopes (Atlassian asks you to pick the Jira site during consent), and return to the integrations page.

​
Step 2 — How the data maps

Open any inbox conversation, open the Jira side-panel, and attach one existing issue from a synced project. The issue should display its key, summary, and status on the conversation.

​
Step 3 — Troubleshooting

​
Calendly — booking events that trigger messaging flows

What it does end to end. On connect, Orbit runs integrations/calendly/connect-complete: it reads your Calendly user and organization URIs, registers a webhook subscription on Calendly pointing at Orbit’s receiver (POST /api/v1/integrations/webhooks/calendly?org=<orgId>), and stores the signing key on your connection record so inbound events verify by HMAC. Every invitee.created and invitee.canceled event then upserts an Orbit contact (linked on the invitee URI) and dispatches a tenant webhook calendly.invitee.created / calendly.invitee.canceled, which your booking flows — SMS/WhatsApp reminders, no-show recovery, reschedule links — consume.

​
Step 1 — Connect and authorize

  1. In Orbit, go to Settings → Integrations, find Calendly, and click Connect.
  2. Sign in to Calendly and authorize the requested scopes.
  3. Return to the integrations page — the connect-complete step runs automatically once the OAuth callback lands.

​
Step 2 — How the data maps

The webhook receiver deduplicates deliveries per event, so Calendly’s retry bursts never duplicate the tenant webhook. The raw payload lands in the calendly_webhook_events audit log for the tenant.
Book a real test meeting on a Calendly event type your account owns with a test email. The invitee should appear as an Orbit contact, and a calendly.invitee.created tenant webhook should fire on your configured outbound webhook endpoint.

​
Step 3 — Troubleshooting

​
DocuSign — envelope events and signer notifications

What it does end to end. Connecting DocuSign starts two syncs: envelopes and recipients. Recipients — signers, cc’d parties, agents — project into the Orbit contacts table, so an envelope’s signer becomes a contact whose timeline carries the envelope state. Orbit can then push signer notifications onto SMS and WhatsApp instead of leaving delivery to DocuSign’s email-only channel, and envelope status tracks alongside the rest of the contact’s conversation history.

​
Step 1 — Connect and authorize

  1. Have a DocuSign account with API access.
  2. In Orbit, go to Settings → Integrations, find DocuSign, and click Connect.
  3. Sign in to DocuSign, authorize the requested scopes, and return to the integrations page.

​
Step 2 — How the data maps

Send a test envelope to an email and phone you control, wait for the recipient sync, then open the matching Orbit contact. The envelope status should appear on the contact, and (with the signer-notification flow enabled) an SMS or WhatsApp nudge should go out on the envelope event.

​
Step 3 — Troubleshooting

​
Slack — real-time alerts and reply-from-thread

What it does end to end. Connecting Slack installs the Orbit app into your workspace and syncs channels. From then on, the integration routes Orbit alerts — new conversations, campaign completion, SLA breaches — to a Slack channel you pick, and an agent can reply to a customer conversation directly from its Slack thread.

​
Step 1 — Connect and authorize

  1. In Orbit, go to Settings → Integrations, find Slack, and click Connect to start Orbit’s Slack install flow.
  2. Choose your Slack workspace and authorize the requested channels and scopes.
  3. Return to the integrations page — the Orbit app installs into the workspace on the OAuth callback.

​
Step 2 — Pick the notification channel and map events

The integration card’s settings expose one channel picker and three independent toggles: Replies from a Slack thread flow back onto the linked conversation in the Orbit inbox — writeback failures are logged and audited but never block the primary send.
Send yourself an inbound test message that opens a conversation, and confirm a new-conversation alert lands in the channel you picked. Reply from the Slack thread — the reply should appear on the conversation in the Orbit inbox.

​
Step 3 — Troubleshooting

For the operator runbook on inbound threads and reply-from-Slack once connected, see Slack onboarding.

​
Zapier — a per-tenant app definition you push yourself

What it does end to end. Orbit does not connect to Zapier over OAuth. The Developer → Connectors page generates a ready-to-publish Zapier app definition, pre-wired to your tenant’s API host, authenticated with your own secret API key. From then on, Zapier exposes the same trigger catalog Orbit webhooks emit and the same action set Orbit’s public API accepts — no new auth, scopes, or provider routing.

​
Step 1 — Create the API key

  1. Open Settings → API Keys and generate a secret key (dv_live_sk_…).
  2. Keep it somewhere safe — you paste it into Zapier once, after import. Use a dedicated key per tool so rotating or revoking one integration does not break others.

​
Step 2 — Download and import the app

  1. Open Developer → Connectors and download the Zapier app definition (orbit-<your-org>.zapier-app.json).
  2. Push it with the Zapier Platform CLI:
  1. When Zapier asks for the API key, paste your dv_live_sk_ secret. The bundled authentication test calls GET /api/v1/me with your X-API-Key header, so Zapier verifies the key before a Zap runs.

​
Step 3 — Wire a Zap and verify

Each trigger (New Inbound Message, Message Delivered, Message Failed, New Contact, Contact Updated, Call Completed, Verification Approved, Campaign Completed) subscribes a REST hook via POST /webhooks and tears it down via DELETE /webhooks/:id — the same webhook CRUD the dashboard uses. Actions (Send SMS, Send WhatsApp Message, Send Email, Create Contact, Create Voice Call, Start Verification) POST to the matching /api/v1 endpoint.
Build a one-step Zap with the New Inbound Message trigger, then send an inbound message to one of your numbers. The Zap should fire within seconds and show the message payload in Zapier’s task history.

​
Step 4 — Troubleshooting

For the full catalog plus the Make and n8n siblings, see Connector downloads.

​
n8n — the community node pack for self-hosted and Cloud

What it does end to end. Like Zapier, n8n skips OAuth. Developer → Connectors generates the definition behind the n8n-nodes-orbit community node pack — an Orbit trigger node plus send/create action nodes, authenticated with your Orbit API key. Teams that already run n8n get first-class Orbit nodes instead of hand-wired HTTP requests.

​
Step 1 — Create the API key

Same as Zapier — one dedicated dv_live_sk_ secret under Settings → API Keys, kept safe for the one paste below.

​
Step 2 — Install the node pack and add the credential

  1. Open Developer → Connectors and download the n8n node definition (orbit-<your-org>.n8n-nodes.json).
  2. Install the n8n-nodes-orbit community pack into your n8n instance — self-hosted or n8n Cloud, same pack.
  3. In n8n, create a credential of type Orbit API and paste your dv_live_sk_ secret. The pack’s trigger and action nodes read that credential.

​
Step 3 — Build a workflow and verify

  • The Orbit trigger node subscribes to one Orbit webhook event (the same catalog the Zapier triggers use) and starts the workflow on it.
  • The action nodes send SMS, WhatsApp, or email and create or update contacts — the same public endpoints the Zapier actions call.
Add an Orbit trigger node subscribed to a New Inbound Message event, wire it to an n8n Set node that echoes the payload, and activate the workflow. Send an inbound message — the execution should show the payload within seconds.

​
Step 4 — Troubleshooting

For the full catalog plus the Zapier and Make siblings, see Connector downloads.

​
Ahead-of-time notes that apply to every one

  • API-route parity. Every dashboard operation above maps to a public route in /api-reference/integrations. POST /api/v1/integrations/connect returns an auth_url; GET /api/v1/integrations reports each integration’s connection state; POST /api/v1/integrations/disconnect severs the connection and clears stored credentials.
  • Tenant-owned controls only. Orbit never asks you to share a provider credential out-of-band, and never exposes one through an API or UI surface. Rotation and revocation are your controls.
  • Inbound vs outbound. These integrations move data into Orbit or between Orbit and the tool — none of them change how outbound messaging routes. (That is deliberate; outbound stays on the Devotel softswitch.)