# Automate ITSM tickets from ServiceNow and Jira Service Management

> A ticket in ServiceNow, Jira Service Management, or Freshservice starts a Stepwork procedure by webhook. It does the work in each admin console and writes the result back to the ticket.

Source: https://stepwork.com/solutions/itsm-ticket-automation

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 procedures
**Best for:** IT Manager, Service Desk Lead, ITSM Administrator
**Outcome:** Routine tickets resolved without waiting in the queue
**Apps:** ServiceNow, Jira Service Management, Freshservice, Microsoft Entra ID, Okta

## 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

## 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
- **Sort the tickets that vendor emails and alerts create:** ServiceNow, Microsoft Teams
- **Set up a new hire's accounts from one ServiceNow ticket:** ServiceNow, Microsoft Entra ID, Internal tool
- **Reset a password or MFA from a ticket, after an identity check:** ServiceNow, Microsoft Entra ID, Microsoft Teams
- **Fill a hardware request from stock, or order it:** ServiceNow, Vendor portal

## 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.

- Create standard change request (ServiceNow)
- Close resolved incidents older than 7 days (ServiceNow)
- Extract open incidents by assignment group (ServiceNow)
- Extract incidents breaching SLA (ServiceNow)
- Create standard intake ticket (Jira)
- Create onboarding ticket set for new hire (Freshservice)
- Close resolved tickets past confirmation window (Freshservice)
- Add user to security groups (Microsoft Entra ID)
- Add user to group (Okta)
- Reset password with forced change (Microsoft Entra ID)
- Reset MFA factors for user (Okta)
- Add a user in an internal admin page (Internal tool)
- Order a peripheral for an employee (Vendor portal)

## More service desk procedures in the Marketplace

Ready-made procedures for queue hygiene, SLA escalation, intake, and access requests.

- Weekly ticket queue hygiene
- SLA breach real-time escalation
- Intake form to tracked work pipeline
- App access request with manager approval

## 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.

- Grant access in an app's admin console: 20 a week, 12 minutes each
- Sort and close a ticket created from email: 30 a week, 4 minutes each
- Set up a new hire's accounts: 2 a week, 90 minutes each
- Reset a password or MFA after a check: 15 a week, 8 minutes each
- Fill or order a hardware request: 8 a week, 15 minutes each

_Example volumes, not a customer's numbers. Minutes are the typical time to do each ticket by hand, including opening the ticket and writing the note. Hours a year assume 50 working weeks._

## 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

## 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.

## Questions

**Q: Does Stepwork replace ServiceNow or Jira Service Management?**
No. People keep filing tickets where they do today, and your queues, SLAs, and reports stay in the service desk. Stepwork does the work between the ticket opening and the ticket closing, then writes the result back.

**Q: How does a ticket start a procedure?**
With a webhook. You add one automation rule in the service desk, such as a ServiceNow business rule, a Jira automation rule, or a Freshservice Workflow Automator step, that sends the ticket to the procedure when it is created or changes status. The ticket's fields arrive as variables.

**Q: What if the app a ticket is about has no API?**
Stepwork works in the app's own screens, the way an admin would, so it does not need one. That covers internal admin pages, on-prem consoles, vendor portals, and SaaS plans that keep user management out of the API.

**Q: Can Stepwork update and close the ticket?**
Yes. The last card of a procedure adds a work note with what changed and sets the status. A procedure can also reassign a ticket, for example to security when a reset request is not confirmed.

**Q: We already use an AI service desk. Where does Stepwork fit?**
Beside it. An AI service desk resolves requests through the APIs of the apps it connects to and hands the rest to a person. Stepwork takes the repeatable ones from that pile, because it works in the app's screens and does not need an API.

**Q: How do we find out which tickets to automate first?**
Send us a ticket export and we will run a free IT ticket analysis. It sorts every ticket into a use case, shows which ones a procedure can run, and estimates the hours that come back over a year.

---

This is the Markdown version of https://stepwork.com/solutions/itsm-ticket-automation, built from the same copy as the page. Everything about Stepwork for AI tools: https://stepwork.com/llms.txt. Book a demo: https://calendly.com/shaun-maclellan/1-1-w-shaun-stepwork
