TriNet + Atlassian Service Collection: Automating HR Workflows

This guide covers how to connect TriNet to Atlassian Service Collection, the use cases it unlocks, and the two integration patterns you’ll set up: a scheduled Assets sync and an event-based webhook integration.

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.

Assets Integration: Importing Employee Data from TriNet Workers 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.
2. Add an Assets data source in OnLink. Configure OAuth authentication using TriNet’s token URL (e.g., https://secure.trinet.com/oauth2/token/) and set the scope to people.
3. Configure the API request. 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.
4. Enable pagination. 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.
5. Map fields to your Assets schema. 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
6. Filter if needed. Add query parameters such as status=active to limit the import to active employees only (confirm the parameter is supported before relying on it).
7. Preview and validate. 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.

Creating TriNet API Datasource

TriNet API Authentication

TriNet Peope API

Full configuration reference: TriNet to JSM Assets

Event-Based Webhook TriNet 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.

Setup steps

1. Review TriNet’s webhook requirements. Check TriNet’s developer documentation for the event types you need (e.g., new hire, status change), authentication requirements, and endpoint specs.
2. Secure the webhook. In your OnLink webhook mapping, set:

   config:auth_scheme=header_token
   config:auth_token=<12-character-random-token>

Generate a random 12-character token, and treat it as a secret — 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 (e.g., new hire). 4. Map the payload to Jira fields. For example:

   key:data.id=customfield_10062
   map:data.first_name=customfield_10063
   map:data.last_name=customfield_10064
   map:data.title=customfield_10065

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 in Jira with the correct fields populated.

Note: If you check the import to Assets option, you can use the same integration to create an Asset object.

Full configuration reference: TriNet Webhook

Get Started

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.

FAQs

1. Does TriNet integrate directly with Atlassian Service Collection (Jira Service Management)? 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.

2. How do I sync TriNet employee data into JSM Assets? 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.

3. Can a new hire in TriNet automatically create a Jira ticket? 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.

4. What’s the difference between the Assets sync and the webhook integration? 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.

5. What do I need before setting up the TriNet–OnLink integration? 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.