Operations Integrations: Source Systems and Data Feeds - Spine Innov Labs

The Operations domain depends on feeds from service desks, workspace suites, documentation tools, and HR systems. Spine Fabric normalizes each feed into a common entity model so practitioners and agents can act on unified data.

Source System	Data Provided	Sync Pattern	Key Entities
ServiceNow	Tickets, assets, vendors, approvals, SLAs	Webhook + nightly bulk	Ticket, Asset, Vendor, Approval
Jira	Project-linked ops issues and vendor problem tickets	Real-time issue webhooks	Ticket, Vendor
Google Workspace	User directory, org hierarchy, license assignments	Directory API with delta sync	Asset (licenses), Approval (delegation)
Notion	Policy pages, process documentation, vendor contracts	Page change webhooks and scheduled crawl	Policy, Process, Vendor
Slack	Request mentions, escalation threads, broadcast channels	Message archive export and keyword listeners	Request (evidence), Ticket (context)
HR/IT systems	Employee records, role assignments, access levels	Scheduled API pull with identity mapping	Asset (assignment), Approval (delegation)

Data Quality and Ownership

ServiceNow is the system of record for tickets, assets, and approvals
Notion is the system of record for policies and process documentation
Google Workspace is the system of record for user identity and license data
HR/IT systems are the system of record for employee-role mappings

When source systems disagree, Spine Fabric surfaces the conflict in the workbench and defers to the designated system of record for that entity type.