Automate ITSM tickets from ServiceNow and Jira Service Management
A webhook from your service desk starts a Stepwork procedure. It does the work in each admin console, with or without an API, then notes and resolves the ticket.
- Use case
- Service desk tickets run as proceduresIT
- Best for
- IT Manager, Service Desk Lead, ITSM Administrator
- Applications used
ServiceNow
Jira Service Management
FreshserviceMicrosoft Entra ID
Okta
- Business outcome
- Routine tickets resolved without waiting in the queue
The problem
Every ticket is a trip to an admin console and back
- Read each new ticket and decide what it is asking for
- Look the requester up and check who has to approve
- Open the app's admin console and make the change by hand
- Repeat it for every app that has no API or connector
- Go back to the ticket, write what you did, and resolve it
- Close the notices and alerts that never needed anyone
Triage
Whatever the ticket asks for, it starts the right procedure
Tickets come from request forms, from email, and from people typing whatever comes to mind. Each service desk sends them to Stepwork the same way, and each one starts the procedure built for it.
ServiceNowCatalog requestRITM0041877 · Application access Requested for: Dana Reyes Application: License portal · Role: AdminGoes to Access request
Jira Service ManagementService requestIT-2291 · New starter Monday
Marcus Lee, hardware engineer. Needs the usual accounts and tools.Goes to Onboarding bundle
FreshserviceTicket from emailSubject: Your certificate expires in 30 days
From: no-reply@certificates.exampleGoes to Inbox and alert triageZendeskTicketlocked out again after getting a new phone, can someone reset my authenticator?Goes to Password and MFA reset
ManageEngine ServiceDesk PlusRequestRequest: USB-C dock and second monitor For: Priya Shah · Desk 4-112Goes to Hardware request
ServiceNowIncident from emailINC0098214 · Budget alert Cloud spend has reached 80% of this month's budget.Goes to Inbox and alert triage
- Access requestFrom
Runs in
ServiceNow
Microsoft Entra ID
Internal tool
Microsoft Teams
- Inbox and alert triageFrom

Runs in
ServiceNow
Microsoft Teams
- Onboarding bundleFrom
Runs inServiceNow
Microsoft Entra ID
Internal tool
- Password and MFA resetFrom
Runs in
ServiceNow
Microsoft Entra ID
Microsoft Teams
- Hardware requestFrom
Runs in
ServiceNow
Vendor portal
Webhooks
How a ticket becomes a run
Your service desk already knows when a ticket opens or changes status. One automation rule sends that event to Stepwork as a webhook, and the ticket's fields become the variables the procedure works from. There is nothing to install in the service desk.
- In your service desk
A ticket opens or changes status
An automation rule matches the ticket by category, form, or status, and sends its fields to the procedure's webhook address.ticket created · access request- Number
- Requested for
- Application
- Access level
- In Stepwork
The fields become variables
The trigger card receives the ticket and hands each field to the cards that need it. Rules pick the path, and each step runs in the app it was recorded in.- Numberbecomes
ticket_id - Requested forbecomes
requester_email - Applicationbecomes
app_name - Access levelbecomes
access_level
- Numberbecomes
- Back in the ticket
The run writes its answer
The last card adds a note with what changed and sets the status. When a step can't finish, the run stops and the run record shows which step.- Work note: what changed, and in which app
- Status: resolved
- Assignment: a person or group, when the procedure hands off
Where the webhook comes from in each service desk
ServiceNowBusiness rule or Flow DesignerSends an outbound REST message when a record is created or updated.
Jira Service ManagementAutomation ruleUses the Send web request action when an issue is created or transitioned.
FreshserviceWorkflow AutomatorUses the Trigger webhook action on a ticket event.ZendeskTrigger with a webhookNotifies an active webhook when a ticket meets the trigger's conditions.
ManageEngine ServiceDesk PlusCustom triggerCalls a webhook when a request matches the trigger's criteria.
Systems
The service desk stays. The work happens in these.
Tickets keep arriving where they do today. Stepwork does the work in the systems each ticket is about: your identity provider, the apps people ask for, and the consoles and portals that have no API or connector. It works through their screens with a login your team grants.
- Service desks: ServiceNow, Jira Service Management, Freshservice, ManageEngine ServiceDesk Plus, Zendesk
- Identity and devices: Microsoft Entra ID, Active Directory, Okta, JumpCloud, Microsoft Intune, Jamf
- Apps people ask for: Microsoft 365, Google Workspace, GitHub, Salesforce, Figma, Zoom, Adobe Creative Cloud
- Consoles and portals with no API: Internal tool, On-prem app, Vendor portal
- Where approvals happen: Microsoft Teams, Slack
Example procedures
Five ticket procedures, card by card
Each one starts from a service desk webhook, takes the path its rule picks, and writes the result back to the ticket. Swap in Jira Service Management, Freshservice, or Okta above each one and the steps stay the same.
Grant access in an app with no API, from a ServiceNow ticket
ServiceNow
Microsoft Entra ID
Internal tool
Microsoft Teams
Step by step
- The ticket starts the runSomeone asks for access to an app through ServiceNow. The service desk sends the ticket to Stepwork as a webhook, with who asked, which app, and which level of access.
- Stepwork finds the personIt looks the requester up in Microsoft Entra ID and reads back their account and their manager. If no account matches, the run stops instead of guessing.
- The rule checks the levelAdmin access takes the approval path. Standard access skips it and goes straight to the change.
- If admin accessAsk the manager to approve in Microsoft Teams
- If standard accessAdd the user in the app's admin console
- The manager approvesOn the admin path only, Stepwork asks the manager in Microsoft Teams and waits for the answer before anything changes.Only on this path: If admin access
- The user is added in the appBoth paths meet here. The recorded flow signs in to the app's admin console and adds the user at the level asked for. It works in the app's own screens, so the app does not need an API.
- The ticket gets the answerStepwork adds a work note with what was granted and resolves the ticket in ServiceNow, so the requester sees it where they asked.
Field map
| From | To |
|---|---|
Sort the tickets that vendor emails and alerts create
ServiceNow
Microsoft Teams
Step by step
- An email becomes a ticketA vendor notice or an alert is sent to the IT address and ServiceNow opens a ticket for it. That ticket starts the run with its subject and body.
- Stepwork reads itAn AI card reads the subject and body and names what it is: a receipt, a renewal, an expiring certificate, a budget alert. If the email has a deadline, the card reads the date.
- The rule decidesThe category decides the path, the same way every time. Receipts, newsletters, and status notices take the top path. Everything else needs someone.
- If a noticeClose the ticket with its category
- If it needs actionSet the category, due date, and owner
- Notices are closedOn the notice path, Stepwork sets the category and closes the ticket in ServiceNow. It stays in your reports and leaves the queue.Only on this path: If a notice
- The rest get an ownerOn the other path, Stepwork sets the category and the due date on the ticket and assigns it to the group that owns that kind of work.Only on this path: If it needs action
- The owner hears about itStepwork posts the ticket and its due date to the owner in Microsoft Teams, so a certificate that expires in 30 days is seen on day one.Only on this path: If it needs action
Field map
| From | To |
|---|---|
Set up a new hire's accounts from one ServiceNow ticket
ServiceNow
Microsoft Entra ID
Internal tool
Step by step
- The onboarding ticket opensHR or a manager files a new-hire ticket in ServiceNow with the person's email and their role. That ticket starts the run.
- The account is createdThe recorded flow creates the account in Microsoft Entra ID with the groups the role starts with.
- Stepwork reads the app listIt reads which apps that role is assigned in Microsoft Entra ID. Each app it finds becomes one pass through the loop.
- The loop sets up each appInside the dashed frame, a recorded flow runs once per app, in that app's admin console. If one app fails, it is marked and the rest still get set up.Repeats: For each app the role needs · 8 apps
- The results come togetherAfter the last app, the Summary card runs once and lists what was set up and anything that needs a person.
- The ticket gets the summaryStepwork adds the summary as a note and resolves the ticket in ServiceNow, so the manager can see what is ready before day one.
Field map
| From | To |
|---|---|
Reset a password or MFA from a ticket, after an identity check
ServiceNow
Microsoft Entra ID
Microsoft Teams
Step by step
- The reset ticket opensSomeone locked out files a ticket in ServiceNow, or the service desk files it for them. The ticket starts the run with who it is for and which reset they need.
- Stepwork finds the accountIt looks the person up in Microsoft Entra ID and reads back their account and their manager.
- The manager is askedStepwork messages the manager in Microsoft Teams and waits for a yes or a no.
- The rule reads the answerA no, or no answer, takes the top path. A yes goes on to the reset.
- If not confirmedHand the ticket to security with a note
- If confirmedReset the password or MFA in Microsoft Entra ID
- Unconfirmed requests go to securityOn the top path nothing is reset. Stepwork adds a note to the ticket and reassigns it to the security group in ServiceNow.Only on this path: If not confirmed
- The reset runsOn the confirmed path, the recorded flow resets the password with a forced change, or clears the MFA factors so the person enrolls again.Only on this path: If confirmed
- The ticket is resolvedStepwork notes which reset ran and who confirmed it, then resolves the ticket in ServiceNow.Only on this path: If confirmed
Field map
| From | To |
|---|---|
Fill a hardware request from stock, or order it
ServiceNow
Vendor portal
Step by step
- The hardware ticket opensSomeone asks for a piece of equipment in ServiceNow. The ticket starts the run with who asked and what they need.
- Stepwork checks the shelfIt searches the asset list in ServiceNow for that item and reads how many are unassigned, with the tag of the first one.
- The rule decidesWith none in stock, the request takes the order path. With one on the shelf, it goes to the assignment.
- If out of stockOrder it in the vendor's portal
- If in stockAssign the asset to the requester
- Out of stock: it is orderedOn the order path, the recorded flow signs in to the vendor's portal, orders the item for the requester, and reads back the order number.Only on this path: If out of stock
- In stock: it is assignedOn the other path, Stepwork assigns the asset to the requester in ServiceNow, so the asset list is right before anyone picks it up.Only on this path: If in stock
- The ticket says what happenedBoth paths end here. The ticket gets the order number, or the asset tag and where to collect it.
Field map
| From | To |
|---|---|
Flows
The flows these ticket procedures are built from
Each flow is one recorded job in one app. Procedures connect them, and any of them can also run on its own from a ticket.
- ServiceNow
Create standard change request
Files a standard change request from a template with schedule and implementation details. - ServiceNow
Close resolved incidents older than 7 days
Bulk-closes incidents that have sat resolved past the confirmation window. - ServiceNow
Extract open incidents by assignment group
Extracts open incidents grouped by assignment group with age and priority into a table. - ServiceNow
Extract incidents breaching SLA
Extracts incidents at or past SLA thresholds with owners and elapsed time.
JiraCreate standard intake ticket
Creates a Jira ticket in the intake project with the standard fields, labels, and priority from the request details.
FreshserviceCreate onboarding ticket set for new hire
Creates the standard set of onboarding tickets (accounts, hardware, access) for a new hire from a template.
FreshserviceClose resolved tickets past confirmation window
Closes tickets sitting in resolved state past the confirmation window in bulk.- Microsoft Entra ID
Add user to security groups
Adds a user to specified Entra security groups that gate app and resource access. - Okta
Add user to group
Opens the target Okta group and adds the specified user, granting the app assignments tied to that group. - Microsoft Entra ID
Reset password with forced change
Resets a user's password in Entra and requires a change at next sign-in. - Okta
Reset MFA factors for user
Finds the user in Okta admin, resets all enrolled MFA factors, and triggers re-enrollment at next sign-in. - Internal tool
Add a user in an internal admin page
Signs in to the internal admin page, creates the user with the role the ticket asks for, and saves the user list afterwards as a timestamped screenshot. - Vendor portal
Order a peripheral for an employee
Signs in to the vendor's ordering portal, adds the item to the cart for the requester, places the order, and reads back the order number.
More procedures
More service desk procedures in the Marketplace
Ready-made procedures for queue hygiene, SLA escalation, intake, and access requests.
- Freshservice · ServiceNow
Weekly ticket queue hygiene
Closes resolved Freshservice tickets past the confirmation window and resolved ServiceNow incidents older than seven days each week, posting the closure counts and any tickets that bounced back. - Zendesk · Slack
SLA breach real-time escalation
Hourly during business hours, extracts tickets breaching or within an hour of SLA from Zendesk, pings the assigned agent, and escalates unacknowledged breaches to the shift lead with account context. 1 more
Typeform · Jira · Asana + 1 moreIntake form to tracked work pipeline
Every few hours, extracts new intake submissions from Typeform, applies routing rules by request type, creates the Jira ticket or Asana task with the mapped fields, and confirms to the requester with the tracking link.1 more
Slack · Okta · GitHub + 1 moreApp access request with manager approval
Takes an access request from Slack, routes an approval to the requester's manager, and on approval branches by app to add the Okta group, GitHub team, or Google group that grants it, confirming back in the thread.
Why Stepwork
The ticket is the record. The run is the proof.
Stepwork is a deterministic agent platform: it runs the steps you recorded in each admin console, in the same order, for every ticket. It works in an app's own screens, so a request does not wait for an API or a connector. Rules decide which path a ticket takes, so admin access always gets its approval and a reset always gets its check. Credentials stay in your vault, and every run records which ticket started it, which path it took, and what changed.
FAQ
Common questions
The math
What these tickets cost a service desk by hand
Example volumes for a company of about 500 people with a service desk of three. Swap in yours.
| The manual task | Times a week | Minutes each | Hours a week |
|---|---|---|---|
| Grant access in an app's admin console | 20 | 12 | 4 |
| Sort and close a ticket created from email | 30 | 4 | 2 |
| Set up a new hire's accounts | 2 | 90 | 3 |
| Reset a password or MFA after a check | 15 | 8 | 2 |
| Fill or order a hardware request | 8 | 15 | 2 |
- Hours a week
- 13
- Hours a year
- 650
- Of one full-time person
- 33%
