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

# Shopify, Zendesk and Okta connect changes (November 1, 2026)

> Connect now asks for your store or workspace address before opening provider sign-in. What each lane syncs once connected, and how to recover if you hit the old error page.

# Shopify, Zendesk and Okta connect changes (November 1, 2026)

On November 1, 2026 the Connect flow for Shopify, Zendesk and Okta changed: Connect now asks for your store or workspace address first, then opens your provider's sign-in page and completes. If you tried any of these three before that date and landed on an error page, retry the connection; the flow that failed now completes.

## Connect a store or workspace

1. Open **Settings → Integrations** and select Shopify, Zendesk or Okta.
2. Enter your address when prompted. Paste the whole address (`acme-apparel.myshopify.com`) or just the first part (`acme-apparel`); either is accepted.
3. Continue. Orbit opens your provider's sign-in page. Approve the connection there.
4. Return to Orbit. The integration card shows **Connected** and the first sync starts on the next scheduled run.

If a connect fails now, check the subdomain you entered against the address shown in your provider's admin console, then retry.

## What syncs after connect

* **Shopify:** customers, orders, products and abandoned checkouts sync into your contacts on a schedule. Order events are available as campaign and journey triggers and branch conditions. For the field-level mapping and the first-journey recipe, see [Shopify integration](https://docs.orbit.devotel.io/guides/shopify-integration.md) and [Abandoned-cart recovery flow](https://docs.orbit.devotel.io/guides/abandoned-cart-recovery-flow.md).
* **Zendesk:** tickets open in the Inbox, and the customer's Zendesk history appears on the Customer 360 timeline. The lane is ticket and customer-context sync; it does not replace your helpdesk's own configuration surfaces. See [Zendesk, Jira, Calendly and more](https://docs.orbit.devotel.io/guides/integrations-zendesk-jira-calendly-docusign-slack-zapier-n8n.md).
* **Okta:** sign-in is delegated to your Okta tenant, and the SCIM provisioning surface keeps your user directory current. Okta does not sync commerce or ticket data. Setup follows [SAML SSO enrollment](https://docs.orbit.devotel.io/guides/saml-sso-enrollment.md) and [SCIM provisioning](https://docs.orbit.devotel.io/compliance/scim-provisioning.md).

## If you saw the old error page

Before November 1, Connect opened the provider sign-in without a tenant address, so the redirect could not be built and every attempt ended on an error page. The failure was on the Orbit side of the handshake; nothing about your account or provider caused it. The address prompt removes that failure, and no other integration's connect flow changed.

For the full connector catalog and console reference, see [Connector hub console](https://docs.orbit.devotel.io/guides/connector-hub-console.md) and [Connected apps](https://docs.orbit.devotel.io/guides/connected-apps.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.