OnLink · HR data

Paychex + Atlassian Service Collection: HR-IT Workflow Automation

OnLink connects Paychex to Atlassian Service Collection in two ways: a scheduled sync of worker data into JSM Assets, and real-time webhooks so HR events such as new hires and terminations create tickets.

Buzz
September 7, 2026
7 min read

Manual notifications vs OnLink

Manual Notification	With OnLink
New hire in Paychex is notified manually through email to IT	Worker record synced into JSM Assets automatically
IT provisioning starts when someone request using a form, email or slack message	Ticket created the moment the new hire event fires
Asset ownership is manually updated	Assets linked to the employee record they belong to
Offboarding is a manual checklist	Termination event triggers the offboarding ticket

Two integration modes

Assets sync

A scheduled pull of every worker from the Paychex API into an Assets object type. Agents see employee, department and status on tickets.

Real-time webhooks

Paychex pushes events (WRKR_ADD, terminations, changes) to OnLink, which creates or updates a ticket or asset immediately.

Assets integration: employee data in your Assets schema

Step by step instructions to connect to Paychex using API:

1. Get Paychex OAuth credentials

Ask your Paychex admin for a Client ID and Client Secret with access to the Workers endpoint.

2. Add an Assets Data Source in OnLink

Enter the Paychex API documentation URL, select Parse, then open the authentication settings.

3. Connect with OAuth

Set the token URL to api.paychex.com/auth/oauth/v2/token and enter your Client ID and Secret.

4. Configure the request

Method GET, URL api.paychex.com/companies/{companyId}/worker, response data path context.

5. Fetch sample data and map fields

Pull a sample response, then map each Paychex field to its Assets attribute (see table below).

6. Preview, then run the import

Confirm the key field is present and unique on every record before saving and running.

Field mapping

Paychex field mapping	Assets attribute
`key:workerId`	Worker ID (unique key, used to match and update existing objects)
`map:employeeId`	Employee Number
`map:employmentType`	Type
`map:job.title`	Job Title
`map:name.preferredName`	Name
`map:supervisor.workerId`	Manager
`map:currentStatus.statusType`	Status

OnLink supports filters, e.g to filter active workers only, add a query parameter such as status=ACTIVE to the request before running the import.

Full walkthrough, including screenshots and pagination settings: Paychex to JSM Assets setup guide.

Webhook integration: tickets the moment HR events fire

Step by step instructions to configure webhook in OnLink:

1. Secure the webhook mapping

In OnLink, set config:auth_scheme=header_token and a random 12-character config:auth_token.

2. Register the webhook in Paychex

Add the OnLink URL, set authentication to APIKEY, and choose the event domain — e.g. WRKR_ADD for new hires.

3. Map the payload to Jira fields

Use key: and map: statements to populate the ticket or asset object (see table below).

4. Choose ticket, asset, or both

Enable Import to Assets if the event should also create or update an asset object.

5. Trigger a test event

Confirm Paychex shows successful delivery, then verify the ticket or asset was created with the right values.

Field mapping (new-hire ticket example)

Webhook field	Jira field
`key:workerId`	Worker ID (unique key)
`map:employeeId`	Employee Number
`map:name.preferredName`	Employee Name
`map:currentStatus.statusType`	Status

Full webhook configuration steps: Paychex Webhook setup guide.

Which mode do you need? Use the Assets sync when agents need the full employee picture on every ticket. Use webhooks when a Paychex event should start work immediately, a provisioning ticket for a new hire or an access-removal ticket on termination. Most teams run both from one Paychex connection. More on event-based imports in Webhooks to Assets.

Before using Onward's apps, my team was manually moving employee data across three systems, creating incredible room for error and wasting valuable time. Today, our onboarding and offboarding workflows are fully automated.

Priya Joshi

HR systems lead, Bark · Atlassian Marketplace review, Jul 2026

Try OnLink for Paychex and Atlassian Service Collection

Sync Paychex workers into Assets and turn HR events into tickets. Start a free trial on the Atlassian Marketplace.

Start free trial

FAQ

Does Paychex integrate with Atlassian Service Collection?

Yes. OnLink connects to the Paychex Flex API and syncs Workers data into Jira Service Management Assets, and can trigger real-time actions in Atlassian Service Collection from Paychex HR events like new hires, terminations, and role changes.

What's the difference between the Assets sync and the webhook integration?

The Assets sync keeps a full, ongoing record of employee data inside your Assets schema. The webhook integration reacts to individual Paychex events in real time, creating or updating tickets and asset objects as they happen, without waiting for the next sync.

Can Paychex events automatically create Jira tickets for IT?

Yes. OnLink’s webhook integration can map any subscribed Paychex event, such as a new hire, to an automated action in Atlassian Service Collection, including creating a provisioning ticket or updating an asset object, without manual entry.

How long does it take to set up the Paychex and OnLink integration?

Most teams complete the initial Assets field mapping and webhook configuration in under an hour, following OnLink’s guided setup for the Paychex API connection and event subscriptions.

Does Paychex integrate with Jira Service Management natively?

Not out of the box. OnLink adds the integration from the Atlassian Marketplace: the Paychex Flex API feeds the Assets sync, and Paychex webhooks drive the real-time ticket automation. The same app covers TriNet, Justworks, Workday, ADP and 20+ other HR systems.

Can I use Paychex data for full onboarding checklists too?

Yes. OnLink handles the data sync and event triggers; OnRamp adds onboarding and offboarding templates with task libraries, and it connects to Paychex as a source. Many customers run both. Paychex worker data can also feed Atlassian Teamwork Graph from the same connection.

Paychex data in Assets

Start a free trial of OnLink on the Atlassian Marketplace. Paychex is one of 100+ HR and payroll sources in the same app.

Try OnLink for Paychex to JSM Assets

Start a free trial of OnLink on the Atlassian Marketplace, follow the Paychex setup guides linked above, and see every other HR, identity and device source the same app connects.