Where supported, Spine can work through the host's existing connector. Other integrations may use an approved workspace-level connection or capability adapter. The integration model depends on the provider, host, tenant policy, and authorized scopes.
Spine Workspace
Keep your tools. Connect the work between them.
The goal is not to rebuild your software stack inside another application. Spine Workspace relates the permitted records, signals, and capabilities that already live across it.
A connection is not a data copy
Common categories of work
- Customer and revenue: accounts, contacts, opportunities, customer commitments, and related activities.
- Communications: email, chat, meetings, calendars, and shared updates.
- Delivery and support: tickets, projects, tasks, incidents, and follow-ups.
- Knowledge: documents, notes, decisions, and source-linked references.
- Operations and finance: approved operational records and workflows.
- Developer environments: issues, code-related activity, release coordination, and permitted tools.
Different providers, common business capabilities
Spine's capability model describes business intent independently of a vendor-specific endpoint. Provider adapters map that intent to the operations and resource traits actually supported by a connection. Not every provider supports every resource or action.
Integration listings state Available, Limited availability, or Planned only after checking the deployed connector and the intended host. No logos or promises that imply an untested commercial integration.
Continue with context