Shopify, Zendesk and Okta are three of the most-requested connectors in the Devotel Orbit integrations hub, and until this month all three shared the same flaw: the Connect button ended on an error page, every time, for every customer. On November 1 we shipped the fix. Connect now asks for the one detail it was missing, and all three lanes complete. This post walks through what changed, what each lane actually syncs, and how to put Shopify order events to work in a journey on day one.
What changed on November 1
Shopify, Zendesk and Okta each sign you in at an address that belongs to your organization: acme-apparel.myshopify.com, acme.zendesk.com, acme.okta.com. Orbit never asked which one was yours, so it had no address to send you to, and the OAuth redirect that every one of these providers requires could not be built. The Connect button failed before your provider was ever involved.
Connect now prompts for that address first, before it opens any sign-in page. Paste the whole address or just the first part; either works. Orbit then opens your own tenant's sign-in, you approve the connection there, and the integration card flips to Connected. Nothing else in the connect flow changed, and every other integration connects exactly as before.
The Shopify lane: what syncs, and where order events go
With the connect path repaired, Shopify is now the complete lane it was meant to be. Once connected, four object types flow from your store into Orbit on a schedule:
- Customers land as contact rows, keyed so repeat buyers merge into one history instead of fragmenting per purchase.
- Orders project their buyer, total, currency and status onto the contact, where the audience builder and journey branches can read them.
- Products sync alongside, so messages and segments can refer to what you actually sell.
- Abandoned checkouts arrive as their own event stream, which is the one commerce teams ask for first.
Beyond the sync, order events are available to campaigns and journeys. A placed order, a paid order, an abandoned checkout: each is a trigger or a branch condition you can subscribe to, the same way you would subscribe to any Orbit event. The Shopify integration guide covers the field-level detail.
A worked journey: the abandoned-cart reminder with an SMS and WhatsApp fallback
The canonical first journey on a Shopify store is the abandoned-cart reminder, and it is four steps:
- Trigger on the abandoned checkout event. The checkout lands on a contact row with the cart contents and the recovery URL, so the journey starts with everything the message needs.
- Wait an hour. A buyer who is still mid-checkout does not need a reminder. An hour is a reasonable starting point; tune it against your store's time-to-purchase.
- Exit on self-completion. Before sending, check whether an order arrived for the same contact in the meantime. Because the order lands on the same row the cart carried, the exit check is a property read on one contact, not a cross-system lookup.
- Send the reminder over SMS, with WhatsApp as the fallback leg. The send step routes the reminder over SMS first and falls back to WhatsApp when the SMS leg cannot deliver, so the reminder still arrives on the channel the customer actually answers.
Like every Orbit send, the reminder passes through your tenant's own controls: quiet hours, suppression lists and consent settings gate it exactly as they gate any campaign. The abandoned-cart recovery flow guide walks the same recipe step by step in the journey builder.
The Zendesk lane: tickets and customer context where agents already work
Zendesk connects with the same address-first prompt (yourcompany.zendesk.com, or just yourcompany). What you get is ticket and customer context flowing into Orbit: a Zendesk ticket opens in the shared Inbox, and the customer's Zendesk history appears on the Customer 360 timeline next to their messages, calls and orders. An agent answering in Orbit sees why this customer is writing without tab-hopping into the helpdesk.
That is the honest scope, and it is deliberately narrow: the Zendesk lane is ticket and customer-context sync, not a two-way helpdesk replacement. If you are evaluating whether Orbit should sit beside Zendesk or replace it, the Zendesk comparison and the integrations walkthrough cover the broader question.
The Okta lane: sign-in and provisioning, delegated to your IdP
The Okta lane is identity, not data sync, and that is what an identity provider should be. With Okta connected, your team signs in to Orbit through your own Okta tenant: authentication stays delegated to the IdP you already administer, with your existing sign-on policies and MFA in front of the dashboard. The SCIM provisioning surface in the product then keeps the user directory current, so joiners get access and leavers lose it without an administrator touching Orbit's user list. Setup follows the SAML SSO enrollment guide and the SCIM provisioning guide.
What the Okta lane is not: it does not sync CRM records, commerce objects or support tickets. It owns who gets in, and it does that job completely.
If you hit the old error page, and why it happened
If you tried any of these three connectors before November 1, you know the symptom: click Connect, wait for the redirect, land on an error page. It was not your account, your plan or your provider. Orbit attempted to start the provider sign-in without knowing your tenant address, and a sign-in redirect with no destination is an error, every time. The failure sat entirely on our side of the handshake.
That is exactly why the fix is a question, not a setting. Connect asks for the address up front, validates it, and only then opens your provider's sign-in. If you abandoned one of these connectors after hitting the error page, go back: the flow that failed you now completes in the same minute. If a connect ever fails today, the cause is a mistyped subdomain, and the prompt tells you so instead of stranding you on an error page.
What each lane is, honestly
- Shopify is now complete: customers, orders, products and abandoned checkouts sync in, and order events drive campaigns and journeys.
- Zendesk is ticket and customer-context sync into the Inbox and Customer 360.
- Okta is delegated sign-in and SCIM provisioning.
No lane pretends to be more than that, and none needs to: between the three, commerce data, support context and workforce identity all sit next to your messaging, voice and campaign tooling instead of in separate tabs. Start from the integrations hub, open the Connectors console guide for the console itself, and read the November 1 changelog entry for the release note.