Salesforce + ServiceNow Integration
Automate Salesforce ServiceNow integration across teams to sync Contacts, Cases, Incidents, and Change Requests seamlessly
Reduce incident resolution time by syncing Cases to Incidents
Eliminate duplicate Contacts and Leads across CRM and ITSM
Improve SLA compliance with automated ticket routing and updates
Today
fragmented customer and incident workflows
- Sales and support teams waste time on manual handoffs, copy-paste updates, and tool switching.
- Customer context gets trapped in siloed systems so Contacts, Leads, Opportunities and Accounts in Salesforce are disconnected from Tickets, Incidents, Problems and Change Requests in ServiceNow.
- That causes missed SLAs, delayed incident resolution, duplicated records, and unhappy customers.
- Managers lack accurate dashboards to measure SLA compliance and root causes across teams.
- Manual escalation chains increase operational costs, slow sales cycles, and create audit gaps hinder improvements.
With Koodisi
Automated Sync with Koodisi
- Koodisi automates Salesforce to ServiceNow sync so Sales, Support and IT share a single source of truth.
- Sync Contacts, Leads, Accounts, Opportunities and Cases from Salesforce with ServiceNow Incidents, Tickets, Problems, and Change Requests.
- Teams get real-time visibility into customer impact, automatic ticket creation from high-value Opportunities, and bi-directional case updates.
- Service teams reduce mean time to resolution, sales reps see support status in Leads and Accounts, and managers track SLAs and handoffs while preserving audit logs and change history.
The sync
What moves, in both directions
Salesforce and ServiceNow stay in step because the sync runs both ways.
Create Incidents from Cases or Opportunities; send Contact, Account, Case, Opportunity and Order details; update priority and SLA timers.
Push Ticket/Incident status, resolution notes, assignments and Change Request approvals back to Cases, Contacts, Accounts and Opportunities.
Faster incident resolution, accurate customer records, and full audit trails improve SLA attainment, reduce operational costs, increase revenue capture on high-value opportunities, and give leaders measurable reports for continuous improvement across Sales, Support, and IT with faster decision-making cycles consistently.
Use cases
What teams automate with this integration
The work that moves between Salesforce and ServiceNow today, and what Koodisi takes over.
Automated customer incident creation from Salesforce
- Trigger: a high-priority Case or Opportunity flag in Salesforce.
- When a Sales rep marks a Case as critical or an Opportunity indicates a service-impacting deal, Koodisi creates a ServiceNow Incident and links the Incident to the Account and Contact.
- Data passed includes Contact, Account, Case details, Opportunity ID, priority, and notes.
- ServiceNow assigns and routes the Incident to the correct support group, while Koodisi updates the Salesforce Case with Incident number and status.
- Outcome: faster response, visible ownership, and synchronized Notes and SLA timers across both systems and audit trails.
Bi-directional case status updates between Salesforce and ServiceNow
- Trigger: ServiceNow Ticket or Salesforce Case status change.
- When a Support engineer changes a Ticket to In Progress or Resolved, Koodisi maps the Ticket fields to the corresponding Salesforce Case and updates status, resolution notes, and attachments.
- Conversely, updates in Salesforce Case comments or priority propagate to ServiceNow as Journal Notes and priority adjustments.
- The flow includes Contact and Account linking to maintain customer context.
- Business outcome: reduced manual updates, consistent customer communications, and a single view of case lifecycle for sales and support teams with measurable SLA improvements monthly.
Sync Accounts and Orders to Incidents
- Trigger: an Order failure or service-impacting Account update in Salesforce.
- When an Order or Account update indicates disruption, Koodisi creates a ServiceNow Incident and attaches Order details, Account references, Contact information, and related Cases.
- The Incident includes Order ID, quantity, delivery status, and priority so IT teams see commercial impact.
- Koodisi also updates the Salesforce Order record with Incident number and status.
- Business result: fewer order-related escalations, faster remediation, clearer post-incident analysis, and preserved audit history for both commerce and IT teams and improved customer retention through proactive communication programs.
Change approvals between Salesforce and ServiceNow
- Trigger: a Change Request or Opportunity milestone in either system.
- When IT creates a Change Request in ServiceNow or a Sales-driven change appears as a Salesforce Opportunity stage, Koodisi routes the request for approvals, synchronizes approval status, and attaches related Configuration Items, Account, and Contact details.
- Approval decisions in ServiceNow automatically update Opportunity or Account records in Salesforce with comments and outcome.
- Outcome: consistent change governance, fewer implementation delays, clear audit logs, and faster rollout of customer-impacting changes with stakeholder visibility and measurable deployment metrics for operations and business leaders.
The workflow
What this looks like when it runs
- Koodisi sits between Salesforce and ServiceNow as a business automation layer that listens for trigger events — like a Case update, Opportunity stage change, or a ServiceNow Ticket status change — and then moves the right customer and operational data where it’s needed.
- You define which fields on Contacts, Accounts, Cases, Opportunities, Incidents, Tickets and Change Requests map to each other so teams see consistent records.
- Koodisi enforces routing rules, retries failed transfers, and logs errors with human-readable explanations so operators can investigate and resolve exceptions quickly.
- The platform uses Koodisi's no-code REST Client for both Salesforce and ServiceNow to authenticate, fetch, and post records without developers writing code.
- Managers get audit trails, SLA metrics, and controls for conditional logic and approvals in a single visual interface.
- The system notifies owners on exceptions, keeps versioned mappings for compliance, and provides dashboards to monitor sync health so leaders can prioritize fixes and audits.
Case → Incident
- 1Case creation or priority change in Salesforce triggers the workflow
- 2Koodisi creates a ServiceNow Incident and maps Contact, Account, Case fields
- 3ServiceNow assigns the Incident to the correct support group and sets SLAs
- 4Koodisi updates the Salesforce Case with Incident number and status for confirmation
Opportunity → Change Request
- 1Opportunity moves to a stage that requires a technical change
- 2Koodisi generates a ServiceNow Change Request and attaches Opportunity and Account details
- 3Approvals and status changes flow back to the Opportunity as comments and status updates
- 4Stakeholders receive confirmations and dashboards reflect approval and deployment progress
Governance
Automated, but still under control
Every run is authorised, recorded, and observable — the part that decides whether automation survives an audit.
Scoped permissions
Role-based access decides who can publish or run the Salesforce and ServiceNow workflows, and who can only watch them.
Every run recorded
Each execution writes an audit trail — what triggered it, what changed, and what the downstream system returned.
Credentials in Key Vault
Salesforce and ServiceNow credentials are stored and retrieved from Key Vault, never pasted into workflow steps.
Traced end to end
OpenTelemetry logs, metrics, and traces show where a run slowed down or failed, rather than reporting one aggregate status.
Routing rules stay readable
Which records sync, and which need approval first, live in a decision table your team can review and change without editing the workflow.
Sensitive fields masked
Personal and commercial values can be masked in logs so an operational record does not become a copy of your customer database.
Ship integrations faster. Operate them without chaos.
Less time on auth, retries, and deployment scripts. More time on the integrations your customers are asking for.
Contact Sales