OnLink · HR data

TriNet + Atlassian Service Collection: Automating HR Workflows

OnLink connects TriNet to Atlassian Service Collection with two patterns: a scheduled sync of TriNet People data into a JSM Assets schema, and event-based webhooks that turn a new hire or termination in TriNet into a Jira ticket or Assets object the moment it happens.

Use cases

New hire onboarding

the moment TriNet marks an employee as active, OnLink creates a JSM ticket to provision hardware, accounts, and access, and/or creates an Assets object for the new employee. This can be done as assets import or a webhook events.

Employee record sync

keep a JSM Assets schema of employees (name, email, title, department, manager, status) automatically up to date from TriNet's Workers/People data, so Assets relationships (asset owner, approver, cost center) stay accurate.

Offboarding and status changes

a status change in TriNet (e.g., termination) can trigger a deprovisioning ticket in JSM, closing the loop on access revocation.

IT asset assignment

link issued equipment (laptops, badges, licenses) to the correct employee object in Assets automatically, instead of manual data entry by IT.

Two integration patterns

Diagram: TriNet People API feeds a scheduled OnLink Assets sync while TriNet webhooks drive real-time Jira tickets and Assets objects
Two patterns, one TriNet connection: a scheduled Assets sync and event-based webhooks.

Assets integration: importing TriNet People data into Assets

This integration pulls employee records from TriNet’s People/Workers API into a JSM Assets schema.

Setup steps

1. Prepare TriNet credentials

 Work with your TriNet administrator to create the OAuth application and collect the Client ID, Client Secret, and Refresh Token. Treat these as secrets.

 Configure OAuth authentication using TriNet’s token URL (e.g., https://secure.trinet.com/oauth2/token/) and set the scope to people.

 Use a GET request against https://api.trinet.com/core/companies/{company_id}/people, with a response data path of data.data. Add includes=department,manager if you want related object details expanded.

 TriNet’s API returns a next_url for large result sets — configure OnLink to follow it so every employee record is imported, not just the first page.

 Set one stable, unique key field (typically employee_number) so OnLink can match and update existing records rather than duplicating them. Typical mappings:

  • key:employee_number → Employee Number
  • map:preferred_name → Name
  • map:work_email → Email
  • map:status → Status
  • map:title → Job Title

 Add query parameters such as status=active to limit the import to active employees only (confirm the parameter is supported before relying on it).

 Run a preview import, confirm the mapped fields match your Assets attributes, and check that the key field is present and unique on every record before scheduling the sync.

Starter field mapping

OnLink mapping
Assets attribute
key:employee_number
Employee Number
map:preferred_name
Name
map:work_email
Email
map:status
Status
map:title
Job Title
Creating a TriNet API data source in OnLink
Creating a TriNet API data source in OnLink.
OnLink authentication settings for the TriNet API
OnLink: OAuth settings for the TriNet API with the people scope.
OnLink endpoint settings for the TriNet People API
OnLink: GET /core/companies/{company_id}/people with response data path data.data and next_url pagination.

Full configuration reference: TriNet to JSM Assets

Event-based webhook integration

We will show you how to configure a TriNet webhook and connect it to OnLink so employee events can create tickets in the configured Jira project or create a Asset Object.

1. Review TriNet's webhook requirements

Check TriNet's developer documentation for the event types you need (new hire, status change), authentication requirements and endpoint specs.

2. Secure the webhook

In your OnLink webhook mapping set config:auth_scheme=header_token and a random 12-character config:auth_token. Treat the token as a secret and never commit it to source control.

3. Register the webhook in TriNet

Work with your TriNet administrator to add the OnLink webhook URL as an endpoint subscribed to the relevant events, such as new hire.

4. Map the payload to Jira fields

Use key: and map: statements to fill the ticket fields (example below). Tick Import to Assets if the same event should also create or update an Assets object.

5. Test end-to-end

Trigger a real or test event in TriNet, confirm delivery, check the OnLink logs for errors, and verify the ticket or Assets object is created with the right values.

Payload mapping example

				
					key:data.id=customfield_10062
map:data.first_name=customfield_10063
map:data.last_name=customfield_10064
map:data.title=customfield_10065
				
			
OnLink webhook setup that turns TriNet events into JSM onboarding requests
OnLink webhook mapping that turns TriNet events into JSM onboarding requests.

Full configuration reference: TriNet Webhook

Today, our onboarding and offboarding workflows are fully automated from Greenhouse to Jira tickets to Workday pre-hires and terminations. The Onward team has been super helpful, and they've created a product that anyone can use - not just developers.
Priya Joshi
Onward customer · Atlassian Marketplace review, Jul 2026
Get started with TriNet and OnLink

If you run HR on TriNet and want to stop re-keying employee data and onboarding tasks into Atlassian Service Collection, start a free trial of OnLink today.

FAQ

 TriNet and Atlassian Service Collection don’t have a built-in connector. OnLink provides a native connection to move data between TriNet’s API and JSM Assets or Jira tickets.

 Configure an OnLink Assets data source with OAuth credentials from TriNet, point it at TriNet’s People API, map fields (like employee number, name, email, and title) to your Assets schema, and set a unique key field so records update instead of duplicating.

 Yes. Set up an OnLink webhook mapping subscribed to TriNet’s new hire event, and configure it to create a Jira ticket and/or a JSM Assets object automatically as soon as the event fires.

 The Assets sync pulls employee data from TriNet on a schedule to keep your Assets schema current. The webhook integration reacts in real time to specific TriNet events (like a new hire or termination) and immediately creates or updates tickets and asset objects.

 TriNet OAuth credentials (or webhook access) from your TriNet administrator, OnLink installed on your Atlassian site, and a JSM Assets schema or Jira project ready to receive the data.

Yes. The same app covers Justworks, Paychex, ADP, Rippling, BambooHR, Workday and 20+ other HR and payroll systems, each with the same two patterns. Full list here.

Yes. The TriNet connection in OnLink can push Workers, Positions and Organizations to Atlassian Teamwork Graph, and OnRamp uses HR events to run onboarding and offboarding templates with task libraries.

On this page

TriNet data in Assets

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

Try OnLink for TriNet to Atlassian Service Collection

If you run HR on TriNet and want to stop manually re-keying employee data and onboarding tasks into Atlassian Service Collection, Give OnLink a try. Start a free trial on the Atlassian Marketplace or talk to our team.

With TriNet connected to Atlassian Service Collection: