Spacebrain Help
Integrations

Connection lifecycle

Verify, monitor, reconnect, migrate, and disconnect provider integrations without surprising dependent workflows.

Verify after authorization

Test the action that matters, not only the green status. Examples include receiving and replying to an email, syncing a search property, posting to a test destination, listing an authorized webinar account, booking a calendar slot, or reading a verified business location.

Record the connected resource name and owner. In providers with several pages, mailboxes, profiles, or properties, a successful authorization can still select the wrong resource.

Monitor connection health

Investigate warnings, sync age, missing data, authorization errors, provider incidents, and invalid-account badges. Provider tokens can expire or be revoked after password changes, administrator policy changes, employee offboarding, consent-screen changes, or prolonged inactivity.

Reconnect

  1. Confirm the connection and dependent module.
  2. Check provider status and the provider account itself.
  3. Reconnect using the intended owning identity.
  4. Approve the required scope.
  5. Re-select the correct resource if prompted.
  6. Test read and write paths separately.
  7. Inspect queued or failed work before retrying.

Migrate ownership

Plan a maintenance window when moving from one provider user, mailbox, page, number, property, or organization to another. Inventory dependents, connect and test the replacement, update senders or destinations, monitor in-flight work, then revoke the old authorization.

Disconnect

Before disconnecting, identify:

  • Agents, inbox channels, email senders, workflows, sequences, campaigns, forms, pages, webinars, social schedules, reports, and agency client requests that depend on it.
  • Scheduled or in-flight actions.
  • Historical data that remains in Spacebrain.
  • Provider-side access that must also be revoked.

Disconnecting Spacebrain and revoking access at the provider are separate operations. Already published posts, sent messages, created events, or provider records generally remain at the provider.

Report a connection incident

Include workspace name, provider, selected resource, approximate time and timezone, last successful action, current status text, and a provider item identifier when safe. Redact customer content, authorization codes, account numbers, tokens, cookies, and secrets.