Integrating ServiceNow means connecting the service platform to the systems that feed it and the ones it hands work to: Workday for joiners, movers and leavers, Jira for engineering escalations, and Salesforce for the customer view. What breaks is ServiceNow's data model: records keyed by sys_id, choice values stored as integers, work notes that must stay internal, and effective-dated changes that sys_user cannot hold.
ServiceNow runs IT service management for larger organisations, often alongside HR service delivery and customer service, and its integrations follow the flow of work through it.
Upstream, Workday is the HR system of record. Completed hires, job changes, org moves and terminations update sys_user records, managers, departments and cost centers, and open onboarding and offboarding lifecycle events. Sideways, incidents, problems and change tasks that need a code fix become Jira issues, with status, comments and the resolution coming back so the service desk can close the incident properly. Outward, account owners in Salesforce see incidents and CSM cases on the account, with ServiceNow states and priorities translated into Salesforce picklists and owners.
sys_id and a human number like INC0010023. Matching on names or emails creates duplicates, so every counterpart needs a stored cross-reference and every write is an upsert.state is a number (1 New, 6 Resolved, 7 Closed) and priority runs 1 to 5 with 1 as Critical. Each needs an agreed translation that fails loudly when someone adds a choice nobody mapped.sys_user is not effective-dated, so future-dated Workday changes have to be held until they apply. And ServiceNow emits no delete event unless the table is audited.Connecting ServiceNow to something not listed here? Tell us which systems are involved and what data has to move. Fixed-price scoping quote within 48 hours.