Orbit's integration marketplace has grown past the workflow pair — the Zapier app and the n8n node pack — into the systems your team already lives in: Salesforce, Zendesk, HubSpot, WooCommerce, and Slack. Each of those now has a public page under /integrations with setup steps, use cases, and an FAQ, and each one is live in the marketplace today — no roadmap label. This post is the announcement of record for the five of them, and it explains the one model they share: message events are written back to your system of record as activities on the matched record, not as full contact copies.
Activity sync, not contact mirroring
The junction is deliberately narrow. A contact, deal, or ticket record is owned by your CRM or store; what Orbit adds is the conversation those records never see. An outbound SMS, a WhatsApp reply, an email from a campaign — each becomes an Activity on the Salesforce record, an engagement event on the HubSpot timeline, or channel context on the Zendesk ticket. Because the write-back targets objects your system already renders, the touches inherit its timelines, reports, and automation triggers instead of landing in a custom table only Orbit can read.
The scope boundary matters for review: this is event-level activity logging, not a full contact replication into Orbit. Salesforce orgs sync contacts, accounts, leads, and opportunities in for agent context and receive message events back as activities; HubSpot syncs contacts, deals, and companies on a 15-minute schedule and receives engagement events back; Zendesk escalates the conversations that need ticket follow-up and imports end-users as Orbit contacts. What moves is defined per integration, and what leaves Orbit toward your system is the activity record — the message and its outcome — under the OAuth scopes you granted.
Which integrations qualify today
Six connections share this model in the marketplace, each with a public page:
- Salesforce (/integrations/salesforce) — bi-directional: CRM records in, message events back as Activities on the record timeline.
- Zendesk (/integrations/zendesk) — inbound conversations escalate to tickets when follow-up is needed; end-users import as contacts.
- HubSpot (/integrations/hubspot) — contacts, deals, and companies sync on a 15-minute schedule; outbound messages log back as engagement events.
- WooCommerce (/integrations/woocommerce) — customers, orders, and products sync from a self-hosted WordPress store; abandoned-cart and post-purchase flows run on SMS and WhatsApp.
- Slack (/integrations/slack) — new-conversation, campaign, and SLA-breach alerts route to a channel you pick; agents reply from the thread.
- The workflow pair, Zapier and n8n, covers the remaining apps — a pre-wired Zapier app and the n8n node pack both fire on Orbit webhook events, so a system without a native connection still joins through the hosted canvas or your own instance.
Connecting — and where the tokens live
Every OAuth-based connection starts in the same place: Settings → Integrations → Connect. The handoff runs through Nango's hosted OAuth service, which means the provider token — your Salesforce org grant, your HubSpot scopes, your Slack workspace authorization — is held in Nango's token store, not in Orbit application code. WooCommerce is the explicit exception: a self-hosted store has no central OAuth authority, so you generate a REST API key pair in WordPress and paste it into the connection card instead. Either way the credential is a tenant-owned control: the scopes you grant are the scopes the sync uses, and revoking at the provider or disconnecting the card stops the flow.
For the scope-sensitive providers — Salesforce orgs, Google Workspace, Microsoft 365 — the first grant typically needs an admin at that end. That is the honest cost of OAuth done properly, and it is the same grant your rep already gave the email-side integration.
Which one fits your team
- Lead-gen and marketing-driven pipeline — connect HubSpot first. Deal and company context lands in the inbox, and every outbound touch posts back to the contact timeline as an engagement event.
- Salesforce-run sales or service orgs — connect Salesforce. The contact–activity junction explainer walks the model record by record, including a Flow pattern for inbound replies.
- Support teams on Zendesk — connect Zendesk. Conversations that need ticket follow-up escalate automatically, and end-user history unifies across channels.
- Commerce on WordPress — WooCommerce gets the same abandoned-cart and order-update flows as a hosted platform, with a pasted key pair instead of an OAuth review.
- Commerce on Shopify — the existing Shopify integration and its cart-recovery post remain the hosted-store path.
- Team visibility — add Slack to any of the above. Alerts route to the channel your team actually watches, and thread replies work bi-directionally.
Pairwise pages cover the common combinations — Salesforce + Slack, HubSpot + Slack, Slack + Zendesk — always with Orbit as the hub, never a direct pipe between the two third-party products.
Frequently asked questions
Is the sync one-way or two-way?
Bi-directional by design: records flow into Orbit so agents get CRM, deal, or ticket context, and message events flow back to your system as activities or engagement events. The exact objects are listed per integration on its page.
Which of these are live today?
All six — Salesforce, Zendesk, HubSpot, WooCommerce, Slack, plus the Zapier/n8n workflow pair — and Stripe for payment events. Roadmap-only entries never get a public page; the directory is gated on what the marketplace actually connects.
Where do my OAuth tokens live?
In Nango's hosted token store. The Orbit Connect flow hands off to Nango for the provider grant, so application code never holds your Salesforce, HubSpot, or Slack token. WooCommerce uses a REST API key pair you paste directly, because a self-hosted store has no OAuth authority to redirect through.
Does every conversation become a Zendesk ticket?
No. Escalation is configurable — only conversations that need helpdesk follow-up create a ticket, not every message.
Can I orchestrate across all of them at once?
Yes — that is what the workflow pair is for. A Zap or an n8n workflow can react to an Orbit event and fan out to whichever connected system should receive it, on top of the native syncs.
Resources
- Salesforce integration page — the junction this post announces, with setup and FAQ
- Salesforce contact–activity junction explainer — the record-by-record model walkthrough
- Zendesk integration page — ticket escalation and end-user sync
- HubSpot integration page — 15-minute CRM sync with engagement write-back
- WooCommerce integration page — self-hosted store, key-pair connect
- Slack integration page — alerts and thread replies
- n8n announcement — the workflow-pair half of this surface
- Integrations directory — every connection listed above
Published 8 September 2026.