Devotel Orbit's integrations marketplace is now announced on two surfaces at once. Inside the product, Settings → Integrations pulls the live provider catalog at runtime — more than 100 providers you can connect without waiting for us — and enriches the ones we ship with setup copy, feature tags, and health status. Outside the product, the public integrations hub holds an in-depth page for every shipped connector — setup steps, use cases, and an FAQ — so a buyer builds their proof shortlist before they ever open a dashboard. This post is the announcement of record for both: it defines what the integration layer actually is, walks the categories it covers, explains how the OAuth handoff and token storage work, and draws the shipped-versus-roadmap line honestly.
The integration layer, defined in one paragraph
Orbit's integration layer moves four kinds of things between your systems of record and your messaging traffic: contacts (the CRM record, store customer, or help-desk end user that a conversation belongs to), activities (message events written back onto that record's timeline), webhooks (Orbit events pushed into automation tools that consume them), and connected accounts (the OAuth-granted link that keeps the first three flowing). The connection itself is deliberately narrow — your CRM owns the record; Orbit adds the conversation the record never sees.
Categories the catalog covers
The marketplace groups providers by the job they do, and the shipped set already spans the six categories below — each linked from the in-app card to a public page:
- CRM — Salesforce and HubSpot: contacts, accounts, deals, and engagements sync, and message events write back as activities on the record.
- Help desk — Zendesk: inbound conversations escalate to tickets; end-users import as Orbit contacts.
- Productivity — Slack: new-conversation, campaign, and SLA-breach alerts route to a channel you pick.
- E-commerce — Shopify and WooCommerce: customers, orders, and products sync; abandoned-cart and post-purchase flows run on your Orbit messaging channels.
- Automation — the Zapier app and the n8n node pack consume Orbit webhook events and call the public API back.
- Analytics — a Segment connection relays Orbit events into whatever downstream warehouse or funnel tool you run.
The in-app catalog also renders every provider the connection layer carries — over 100 of them — even where no public page exists yet. Those rows get generated status and connect affordances from the catalog itself; when we add authored copy, the richer card replaces the fallback automatically.
The OAuth handoff, and where tokens live
Connecting a provider never means pasting credentials into a form and hoping. Connect opens a hosted authorization popup — the OAuth consent screen belongs to the provider you are linking, so the scopes you grant (read contacts, write activities, and the like) are presented and approved on their domain, not ours. Tokens are stored by the hosted auth layer that brokers the connection and are refreshed in the background there; Orbit reads the action-level permissions it needs over the provider API, and the credentials never sit inside Orbit application code. When a provider revokes or invalidates a stored token — someone rotates a key, or an admin revokes access — the affected card surfaces a reconnect-required state in the dashboard instead of failing silently, and one click re-runs the same hosted flow.
Two exceptions are handled on their own rails: self-hosted stores (WooCommerce) connect with a credential paste because there is no hosted provider to delegate to, and some providers accept an API key directly. The rule holds either way — the connect flow is declared per provider, and secrets live in the credential store, not in workspace settings.
What shipped on the public hub
The public hub at /integrations currently carries roughly twenty pages — one per shipped connector, plus a handful of curated pairwise pages for combinations buyers actually shortlist together (connect both sides to Orbit; Orbit is always the hub). The launch set covers salesforce, hubspot, shopify, woocommerce, slack, n8n, and zendesk, each with ordered setup steps, use cases, and an FAQ picked up by answer engines.
The buyer journey this enables is deliberately short: search a connector, land on its page, read the setup steps it takes, and put Orbit on the proof shortlist — before signing up, before a sales call. The count difference between the two surfaces is intentional, and worth stating plainly: the dashboard catalog lists ~100 providers because it mirrors the live connection layer; the public hub documents the ones we have authored in depth, and it grows one authored page per shipped connector rather than spewing stub pages for the whole roster.
Shipped versus roadmap, stated plainly
A few visible cards are roadmap-only — Google Sheets, Freshdesk, a customer-managed S3 bucket, and Mixpanel are the current four. They are deliberately excluded from the public hub: the directory's contract is that every page describes a connector you can connect today, so a roadmap row earns a public page only when the connection is actually live. Inside the dashboard the hint works the other way too — mark a roadmap row as coming soon only until an admin wires the provider on the connection side; once it is live there, the live row wins and the hint drops away. In short: the in-app catalog tells you what you can connect right now (100+ providers), the public hub tells you what we have documented in depth (~20 pages), and roadmap rows are labeled as such on both surfaces — no connector is advertised before it exists.