Orbitr field guide

Integrations

Connect site-scoped evidence and a supported publishing surface without crossing tenant or property boundaries.

Evidence integrations

Google Search Console provides search performance for a selected property. Google Analytics views may be available where enabled for the account. Provider access and property selection are separate steps.

Publishing integrations

Orbitr has publishing paths for supported WordPress, Shopify, Webflow, Wix, and GitHub-backed configurations. Availability is discovered from the account, site, provider grant, and requested task. Seeing a platform name does not guarantee that every resource or mutation shape is supported.

Site scope

Every provider read and write is associated with an Orbitr site. A provider account, property, repository, or CMS resource that is not linked to the active site is not treated as valid evidence or a valid publishing target.

Token and permission failures

Expired tokens, revoked grants, missing scopes, and provider permission changes block the affected operation. Reconnect the integration and reselect the exact resource rather than creating a second site to work around the error. An expired OAuth callback must be restarted from Orbitr instead of replayed.

Safe connection checklist

  1. Select the Orbitr site.
  2. Connect the provider account.
  3. Select the exact property or publishing resource.
  4. Run the integration test.
  5. Confirm that the requested task is supported and reversible.
  6. Start with one bounded task.
  7. Verify the public result and retain the operation or snapshot identity.