> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Zendesk, Calendly, DocuSign, and Jira: the OAuth SaaS integrations

> One walkthrough for the OAuth-popup integrations — Zendesk, Calendly, DocuSign, Jira. Connect from the Integrations hub, pick the per-integration setup details, monitor health, and revoke safely.

# 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](/guides/connectors-download)); the four below are direct OAuth connections.

| Integration  | What it does                                                                                                                                                                     | Feature tags                         |
| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ |
| **Zendesk**  | Converts inbound conversations into Zendesk tickets; imports Zendesk end-users as Orbit contacts, so customer history is unified across the helpdesk and the messaging channels. | CRM context, agent tools, automation |
| **Calendly** | When an invitee books, Orbit fires SMS/WhatsApp reminders, no-show recovery, and reschedule-link flows — fully templated and channel-aware.                                      | Engagement, automation               |
| **DocuSign** | Pushes signer notifications onto SMS/WhatsApp instead of relying on DocuSign's email-only delivery; tracks envelope status alongside conversations.                              | Engagement, automation               |
| **Jira**     | Surfaces Jira issues inside the inbox so agents link bug reports to conversations; AI agents can open and update issues on behalf of reps.                                       | Agent tools, automation              |

<Info>
  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.
</Info>

***

## 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:

```bash theme={null}
curl -X POST https://api.orbit.devotel.io/api/v1/integrations/connect \
  -H "X-API-Key: dv_live_sk_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{ "integration_id": "zendesk" }'
```

**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.

<Check>
  After consent, check `GET /api/v1/integrations` — the row for your provider reports a connected state.
</Check>

***

## 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:

| Integration  | Post-connect step                                                                                                                                                                                              |
| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Zendesk**  | Confirm the entity mapping — Open the drawer's **Data** tab and enable the tickets and users models. Tickets from inbound conversations map to your Zendesk default group; end-users import as Orbit contacts. |
| **Calendly** | Pick reminder templates — **Flows → Templates → Calendly**: choose the reminder window (24h/1h is the default pair), the no-show recovery flow, and the reschedule-link copy.                                  |
| **DocuSign** | Link envelopes to conversations — notifications post as their own conversation thread in the inbox, so envelope status (sent → viewed → completed) is tracked next to signer messages.                         |
| **Jira**     | Enable the Jira agent tool — under **Agents → your agent → Tools**, enable the Jira toolset so AI agents can open and update issues; synced issues surface in the inbox CRM panel.                             |

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:

```bash theme={null}
curl -X DELETE https://api.orbit.devotel.io/api/v1/integrations/zendesk/disconnect \
  -H "X-API-Key: dv_live_sk_your_key_here"
```

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:

| Integration | CRM context | Agent tools | Automation | Engagement |
| ----------- | ----------- | ----------- | ---------- | ---------- |
| Zendesk     | ✔           | ✔           | ✔          | —          |
| Calendly    | —           | —           | ✔          | ✔          |
| DocuSign    | —           | —           | ✔          | ✔          |
| Jira        | —           | ✔           | ✔          | —          |

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

* [Connect HubSpot & Salesforce end to end](/guides/hubspot-salesforce-integration) — the CRM-context providers with deeper data models, covered in their own walkthrough.
* [Connect Intercom end to end](/guides/intercom-integration) — the bespoke OAuth install (signed-state round-trip), for comparison with the popup flow documented here.
* [Build your first flow](/guides/build-first-flow) — wire the inbound ticket/booking/envelope events into channel flows.
* [Integrations API reference](/api-reference/integrations) — connect, status, sync, data, and disconnect endpoints with worked examples.
* [Webhook consumer guide](/guides/webhook-consumer) — how Orbit treats inbound provider webhooks generally (signature verification, retry windows, idempotency).
* [Downloadable connectors for Zapier, n8n, and Make](/guides/connectors-download) — when the workflow engine lives outside Orbit.