Skip to main content

​
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 and Abandoned-cart recovery flow.
  • 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.
  • 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 and SCIM provisioning.

​
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 and Connected apps.