Workday to ServiceNow, JSM or Freshservice: automating joiner, mover and leaver tickets

Who this guide is for

This guide is for IT, HR technology and service desk leads at companies that run Workday as their HR system of record and want new hires, internal transfers and terminations to create the right IT work automatically, in ServiceNow, Jira Service Management (JSM) or Freshservice. It is written for the people who will actually build it: the Workday integration owner, the ITSM platform admin and the identity or security lead who cares about leavers.

We only describe official connectors and APIs: what Workday, ServiceNow, Atlassian and Freshworks document themselves. Sources, all checked on Nov 7, 2026: the ServiceNow Workday HR spoke documentation, the ServiceNow guide to Workday HR spoke webhooks, the ServiceNow guide to configuring the Workday REST API, the HR Service Delivery Integration with Workday documentation, Atlassian's Atlassian "Use Workday with Automation" documentation and Atlassian journey trigger documentation, Freshworks' Freshservice Integration with Workday support article and Workday Connector App listing, and Workday's Workday developer documentation on integration setup and Workday Integration Cloud datasheet. Opinions on design and fit are ours, from building JML flows, and are labelled as such.

What a joiner, mover or leaver ticket actually needs

Before choosing a connector, be clear about what the ITSM tool must receive. In our experience most failed JML projects did not fail on the API. They failed because nobody agreed which Workday event means "start the work", which fields are trustworthy on that date, and who owns the exceptions.

Three design facts apply whichever ITSM tool you pick:

• Workday events are effective-dated. A hire entered today may take effect in six weeks. Your flow must store the effective date and schedule work against it, not against the time the event arrived.
• Events can be corrected, rescinded or cancelled. Atlassian's documentation, for example, lists worker statuses of Completed, Corrected, Canceled, Rescinded, Denied and Manually advanced for its Workday trigger. A rescinded hire must cancel the onboarding ticket and any ordered kit.
• The ITSM tool is the work tracker, not the identity system. Many organisations provision accounts from their identity provider. The ticket coordinates the human work (hardware, desk, approvals, application access the IdP cannot grant) and records evidence for audit.

The three official integrations at a glance

This table summarises what each vendor documents as of Nov 7, 2026. "Out of the box" means a documented, vendor-supported component, not something you can build with enough scripting.

Our read: ServiceNow has the broadest Workday surface area, JSM has the simplest and cheapest joiner path, and Freshservice has the most complete packaged JML recipes for a mid-market tool. None of them removes the need for Workday-side configuration, which is where most of the effort sits.

The Workday side: what you configure regardless of ITSM tool

Every option starts in Workday. Workday's own developer documentation describes the integration technologies available: inbound and outbound Enterprise Interface Builder (EIB), template-based integrations and connectors (including Core Connectors), Orchestrate for Integrations, Workday Studio, the SOAP-based Workday Web Services (WWS) API, REST APIs and Report-as-a-Service (RaaS). For JML into an ITSM tool, the vendor connectors above rely on a small subset of these.

Practical rules we apply on the Workday side

• One ISU per integration system, with the narrowest domain permissions that work. Freshworks' partner guidance and Atlassian both recommend ISUs rather than personal accounts, because a personal account breaks the integration when that person changes role or leaves.
• Design the RaaS report first. Agree the columns IT needs (see the table above), test it in a sandbox tenant and only then wire the ITSM side.
• Decide which transaction types count as joiner, mover and leaver events in your tenant. Workday administrators name and configure business processes differently, and Freshworks explicitly tells customers to get the exact transaction names from their Workday administrator.
• Record the tenant time zone. ServiceNow's HRSD integration documentation requires the Workday tenant time zone field even if you do not use worker profile sync; Freshservice asks for it at install too.

ServiceNow: the Workday HR spoke

ServiceNow's documented route is the Workday HR spoke in Integration Hub. Per the ServiceNow Workday HR spoke documentation, the spoke is built by Bristlecone, Inc., requires an Integration Hub subscription, and uses both the Workday SOAP API and the REST API. Workday-side prerequisites include registering an ISU (with UI sessions disallowed) and a security group with the required domain permissions.

What the spoke gives you for JML

The webhook setup is documented step by step in the ServiceNow guide to Workday HR spoke webhooks: create a Workday Webhook Registry record per event (for example CreateUser), generate the credentials ServiceNow will accept, then configure Workday to call the callback URL with those credentials. REST actions need an OAuth client registered in Workday and an OAuth provider and connection configured in ServiceNow, as described in the ServiceNow guide to configuring the Workday REST API.

How we build JML on ServiceNow

• Joiner: Create User subflow creates or updates the user; a Flow Designer flow then submits an onboarding order guide with catalog tasks for hardware, accounts and facilities, scheduled from the Workday start date.
• Mover: there is no packaged "transfer" subflow, so we run a scheduled flow that downloads a RaaS report of job changes with effective dates, compares old and new values, and raises a mover request only when something IT cares about changed (department, location, manager, job profile).
• Leaver: Deactivate User webhook or a scheduled termination report raises an offboarding request with tasks for asset recovery, access removal and mailbox handling, timed to the termination date in the right time zone.

Jira Service Management: Workday in Automation and Journeys

Atlassian added Workday as a native component in Jira Automation. Per the Atlassian "Use Workday with Automation" documentation, it is available to JSM Cloud customers on Standard, Premium or Enterprise, and a Jira admin connects it using a Workday API client.

How we build JML on JSM

• Joiner: use the native trigger, retrieve worker details, and create the parent onboarding work item with a request type; let a journey create child work for IT, facilities and the manager. Filter out Rescinded and Canceled statuses, and add a branch that cancels open onboarding work if a later event rescinds the hire.
• Mover: a scheduled Automation flow calls a RaaS report (JSON format) with the custom request action. Atlassian's own tip recommends RaaS for pulling only the data you need, for example workers starting in the next three months. Create a mover request per row where tracked fields changed.
• Leaver: the same scheduled pattern with a termination report, creating offboarding work items timed to the termination date. Sensitive exits should not wait for a schedule; give HR a restricted request type to raise them immediately.

Atlassian's published setup does not describe termination or transfer events for the native trigger, so we treat movers and leavers as report-driven builds on JSM. If Atlassian extends the trigger, the design gets simpler, but do not plan a go-live on an undocumented capability.

Freshservice: the Workday Connector App

Freshworks publishes a Workday Connector App, listed as "Verified by Freshworks" and "available for Pro & Enterprise plans only" on the Workday Connector App listing. The Freshservice Integration with Workday support article describes the scope: Workers and Contingent Workers, with these recipes:

Triggers are either a real-time new or updated business object (Workers or Contingent Workers) filtered by transaction type, or a scheduled report fetch using a custom JSON report when the right transaction types are not available or you need to restrict the data. The user-sync checklist explicitly allows limiting syncs to changes such as location or department, which is the closest thing to packaged mover handling in the three tools.

Connector tasks are the variable cost

Connector Apps consume tasks. On the Freshservice pricing page (checked Nov 7, 2026), Connector App Tasks are included on Pro and Enterprise with a one-time free credit of 500 tasks, then priced at $80 / £65 per 5,000 tasks, valid until the end of the billing cycle. The support article adds detail that matters for budgeting: enabling the Workday widget runs a one-time mapping that consumes roughly the number of employees multiplied by 3 tasks, and each widget look-up consumes 3 tasks. Run the recipes in test mode, as Freshworks recommends, and estimate monthly task use before go-live.

What it costs (checked Nov 7, 2026)

Only vendor list prices are shown. Workday, ServiceNow and Integration Hub are quote-only and are not estimated. Freshservice publishes official USD and GBP prices. Atlassian publishes USD only, so the GBP figures for JSM are indicative conversions.

Indicative GBP conversions use the Bank of England daily spot rate (series XUDLUSS) of US$1.3476 per £1 for 5 Nov 2026, the latest published when we checked on Nov 7, 2026. They are not official UK prices; the vendor does not publish a GBP list price, and your invoice currency, rate and VAT treatment may differ. Atlassian pricing is progressive, so the per-agent figure changes with your agent count and billing period. Prices exclude VAT and other taxes.

A worked example on list prices only: 10 Freshservice Pro agents on annual billing is 10 × $99 × 12 = $11,880 a year, or 10 × £79 × 12 = £9,480 a year on the official UK price, before connector task top-ups. We do not show a JSM figure for 10 agents because Atlassian's calculator price at 10 agents is not the 75-agent figure above; run Atlassian's calculator for your count.

Design rules that prevent JML incidents

Movers are where we see the most noise. A transfer often changes several fields at once, and some changes (cost centre) mean nothing to IT. Filter on the handful of fields that change access, and route everything else to a weekly report rather than a ticket.

Best for, and wrong choice when

A phased rollout that works

• Phase 1, discovery: agree the JML event map, fields and owners with HR; design the RaaS reports; set up the ISU, security group and API client in a Workday sandbox.
• Phase 2, joiners: go live with joiner tickets only, with rescind handling. Measure how many hires arrive with complete data before the start date.
• Phase 3, leavers: add termination-driven offboarding, including the immediate path for sensitive exits. Reconcile against HR's leaver list for the first cycles.
• Phase 4, movers: add mover requests last, filtered to access-relevant field changes.
• Phase 5, write-back and reporting: push status back to Workday where your tool supports it, and report on time-to-ready for new hires and time-to-revoke for leavers.

Moving ITSM platform at the same time? Do not combine a platform migration with a new Workday integration in one cutover. Finish the move first (our ServiceNow to Freshservice and ServiceNow to JSM migration guides cover the sequencing), then add JML.

Frequently asked questions

Related articles