Skip to main content

​
Connect Zendesk, Calendly, DocuSign, and Jira end to end

Four shipped integrations — Zendesk, Calendly, DocuSign, and Jira — connect with the same generic OAuth popup, so this guide covers the shared flow once and the per-integration details in tables. Each of them feeds a different Orbit surface: Zendesk tickets into the inbox, Calendly bookings into reminder flows, DocuSign envelopes into tracked conversations, and Jira issues into the inbox CRM panel.

​
Step 1 — Find the cards in the Integrations hub

Open Settings → Integrations. The card grid is loaded at runtime from the integration server’s provider registry via GET /api/v1/integrations/catalog, so providers your platform admin wires up appear without a code change. Orbit layers marketing copy, icons, and feature tags on top of what the registry returns; a provider the registry does not expose renders with a generic icon and automation category until the admin wires it. Roadmap entries — Freshdesk and Mixpanel among them — show with a Coming soon badge. They go live when the provider is wired on the platform side; no action on your side until then.

​
Step 2 — What each integration does

Pick the integration for the capability you need. Zapier, n8n, and Make are separate connectors (see the connector downloads guide); the four below are direct OAuth connections.
Zendesk, Salesforce, and HubSpot are the CRM-context providers — the inbox contact panel shows synced records from whichever you connect. Connect only the systems you use.

​
Step 3 — Connect via the OAuth popup

These integrations use the generic connect flow — not the bespoke install routes that Bridge, Intercom, Slack, and WooCommerce carry. You can trigger it either from the dashboard or from the API; both open the same provider consent screen. From the dashboard: click Connect on the integration card, sign in at the provider’s consent screen, and grant the requested scopes. When consent completes, the card status flips to Connected and the drawer opens with the integration’s settings tabs. From the API: request the auth_url and redirect the operator there:
Owner or admin role required, plus the integrations:write scope on the API key. Valid integration_id values for the popup flow are zendesk, calendly, docusign, and jira; provider credentials are encrypted at rest and token refresh is handled for you.
After consent, check GET /api/v1/integrations — the row for your provider reports a connected state.

​
Step 4 — Finish the per-integration setup

The popup gets the account connected; each integration then has its own short setup step in the card drawer: Pull records on demand any time with POST /api/v1/integrations/{id}/sync and read the synced record set with GET /api/v1/integrations/{id}/data?model=….

​
Step 5 — Monitor connection health

The card badge reports the live health of the connection: Connected (healthy) or Errored (revoked token or provider outage). The drawer’s Settings tab shows the connected timestamp and the sync log, and GET /api/v1/integrations/{id}/status exposes the same signal over the API. A revoked token or an expired grant shows as errored until you reconnect; reconnecting runs the same popup and refreshes the stored credentials in place.

​
Revoke or rotate the connection

From the dashboard: open the integration’s drawer and use Revoke in the Settings tab — Orbit disconnects and asks the provider to delete the grant. From the API, revoke with the disconnect endpoint:
The provider-side permissions are narrow — ticket, user, calendar, or document scopes — so revoking on the Orbit side is enough; rotate a leaked provider credential in the provider’s own admin panel and reconnect.

​
Feature matrix — what each tag unlocks

The cards carry feature tags that name the Orbit capability the integration feeds. The complete matrix for the OAuth-popup cohort: Read the tags as: CRM context — synced providers surface in the inbox contact panel and customer 360; Agent tools — AI agents can act on the provider’s records mid-flow; Automation — inbound events drive Orbit flows (tickets, reminders, envelope updates); Engagement — outbound SMS/WhatsApp touches tied to the provider’s lifecycle (bookings, envelopes).

​
Where the data lands — cross-references