ServiceNow + Microsoft Teams Integration
ServiceNow integration with Microsoft Teams that goes beyond the native connector — two-way ticket, approval, and Work Note sync, no code.
Reduce incident resolution time by automating ticket notifications
Improve SLA compliance with real-time incident updates and reporting
Centralize approvals and preserve audit trails across systems
Today
Fragmented incident communication
- Manual handoffs create missed SLAs and frustrated teams when ServiceNow incidents, Tickets, Change Requests, and Contacts are not shared with front-line staff in Microsoft Teams.
- Support, NOC, and Dev teams waste time duplicating incident details, searching for related Contacts or Change records, and chasing approvals.
- These gaps mean slower resolution, poor audit trails, repeated work, and dissatisfaction across ITSM and support workflows.
- Manual status updates, disconnected Approvals, and inconsistent Ticket priorities cause escalations and erode trust between teams and stakeholders.
With Koodisi
Automated Sync with Koodisi
- Koodisi automates two-way sync so ServiceNow Incidents, Tickets, Change Requests, Approvals, and Contact updates flow into Microsoft Teams channels, private chats, and adaptive cards.
- Teams receive contextual messages with Incident fields, Priority, State, assigned Group, and related Contact details.
- Conversely, Teams messages, approval actions, and comments can create or update ServiceNow Tickets and Work Notes.
- The result: faster incident routing, clearer ownership, fewer escalations, and traceable audit trails across IT and business teams.
- Managers receive SLA trend reports automatically daily.
The sync
What moves, in both directions
ServiceNow and Microsoft Teams stay in step because the sync runs both ways.
New Incidents and Tickets post adaptive cards to channels with Priority, Assignment Group, Contact, Work Notes, attachments, SLA breach alerts, and approval requests.
Approvals, comments, or flagged messages in Teams create or update ServiceNow Tickets, append Work Notes or Comments, change Assignment, and attach uploaded files to the Ticket.
The integration speeds mean-time-to-resolution, improves update accuracy, reduces duplicate work, and preserves audit trails so managers can prove compliance, measure SLAs, and continuously optimize cross-team workflows with clear ownership and timestamped evidence across IT, support, product, and customer success teams.
Use cases
What teams automate with this integration
The work that moves between ServiceNow and Microsoft Teams today, and what Koodisi takes over.
Automated Incident Triage and Team Notification Flow
- When a high-priority Incident is created in ServiceNow, Koodisi triggers an automatic Teams channel notification that includes Incident number, Priority, Short Description, Assignment Group, and Contact details.
- The flow posts an adaptive card with Approve/Assign buttons; an approval or comment in Teams appends a Work Note to the ServiceNow Ticket and updates Incident State.
- This reduces handoff delays, ensures on-call engineers see context immediately, and creates a timestamped audit trail linking the original Incident record to the Teams conversation.
- Managers receive SLA alerts and resolution metrics without manual reconciliation daily.
Channel-driven Ticket Creation from Teams Messages
- When a customer message or sales request appears in a Microsoft Teams channel, a Teams bot or a teammate can flag that conversation to create a ServiceNow Ticket.
- Koodisi captures the message text, reporter Contact, attachments, and channel metadata, then populates a new Incident or Service Request in ServiceNow with Priority, Category, and Related CI fields.
- The Ticket links back to the original Teams thread, enabling agents to continue the conversation in Teams while updates, status changes, and closure events sync automatically to the Team channel and preserve audit context.
Approval Workflows via Teams Adaptive Cards
- When a Change Request or Approval task is pending in ServiceNow, Koodisi posts an adaptive card to the responsible approver's Microsoft Teams chat or channel.
- The card shows Change number, Requested By Contact, Impact, Risk, and proposed Schedule.
- Approvers can Approve, Reject, or Add Comments directly in Teams; those actions update the ServiceNow Approval record, trigger SLAs, and append Work Notes.
- Automated reminders and escalation messages are sent on missed approvals, ensuring faster approvals and clear, auditable decision history tied to the original ServiceNow Change.
- Managers get approval time reports.
Cross-team Incident Escalation with Alerts and SLA Notifications
- When an Incident breaches a threshold or a monitoring alert creates a Ticket in ServiceNow, Koodisi escalates the case by posting an urgent message to an on-call Microsoft Teams channel and tagging the right Assignment Group.
- The message contains Incident ID, Priority, Affected CI, Contact info, and current SLA status.
- Team members can acknowledge in Teams, which updates the ServiceNow Incident and pauses escalation timers.
- Automated follow-ups, status updates, and closure notifications sync back to Teams so leadership sees resolution progress without manual updates.
- Auditable timestamps and ownership improve compliance.
The workflow
What this looks like when it runs
- Koodisi sits between ServiceNow and Microsoft Teams to orchestrate events and data so teams can focus on work instead of copying updates.
- When a trigger event occurs — for example a new Incident, an Approval request, or a Ticket comment — Koodisi detects it, maps the relevant fields (Incident number, Priority, Assignment Group, Contact, Work Notes) to a Teams message or adaptive card, and sends a formatted notification.
- If someone acts in Teams, the action maps back to ServiceNow, updating the Ticket or Approval record.
- Koodisi shows mapping rules in a visual canvas and catches exceptions, routing errors to an operations channel and retrying or alerting maintainers.
- You configure connections using Koodisi’s no-code REST Client for both ServiceNow and Microsoft Teams, so the integration is maintainable by ops teams without developer handoffs.
- Dashboards summarize sync health, failed items, and latency so managers can prioritize fixes and audit changes in one place.
Incident → Teams Channel
- 1New high-priority Incident in ServiceNow triggers the workflow
- 2Koodisi extracts Incident fields and formats an adaptive card message
- 3Teams channel receives the adaptive card with Incident details and action buttons
- 4Approver or engineer action in Teams updates ServiceNow and posts confirmation
Teams Message → ServiceNow Ticket
- 1A teammate flags a Teams conversation to create a Ticket
- 2Koodisi captures message text, reporter Contact, and attachments
- 3ServiceNow creates a new Incident or Service Request with mapped fields
- 4The Ticket links back to the Teams thread and notifies the channel
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 ServiceNow and Microsoft Teams 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
ServiceNow and Microsoft Teams 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.
Use Koodisi’s visual workflow builder to connect ServiceNow and Microsoft Teams without code. Add two connectors using Koodisi’s no-code REST Client for both ServiceNow and Microsoft Teams, drag a trigger (for example, Incident created), map fields visually, and activate the workflow. Koodisi handles authentication, retries, logging, and error notifications.
The ServiceNow Teams integration posts ServiceNow Incidents, Tickets, and Approvals into Microsoft Teams channels as adaptive cards, and writes approvals and comments made in Teams back to ServiceNow Tickets and Work Notes. Koodisi builds this ServiceNow integration with MS Teams through its no-code REST Client, so you choose which records, channels, and fields are included.
Yes — Koodisi supports near real-time event-driven sync for triggers like Incident creates or Approval actions, and configurable polling for systems that require batching. You can choose immediate push updates for critical Tickets and SLAs, or scheduled batch syncs for lower-priority records to reduce API usage and control timing flexibility.
Common sync objects include Incidents, Tickets, Change Requests, Approvals, Contacts, and Service Requests. Fields such as Priority, State, Assignment Group, Short Description, Work Notes, and attachments can flow. Events like Incident created, SLA breach, comment added, and approval completed trigger notifications and updates so Teams reflects the ServiceNow record state.
Koodisi’s no-code visual builder removes the need for custom development. Ops teams configure triggers, map fields, and activate workflows with the no-code REST Client for ServiceNow and Microsoft Teams. Complex decisions are modeled visually so no hand-written code is required.
ServiceNow's native Teams integration covers Virtual Agent chat and one-way notifications configured inside ServiceNow. Koodisi adds two-way sync — approvals, comments, and flagged messages in Teams write back to ServiceNow Tickets, Approvals, and Work Notes — configured visually instead of through ServiceNow's notification engine, and via the same no-code REST Client you'd use to connect ServiceNow to Slack, Salesforce, or any other system.
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