Pyn + Jira
Connect Jira to Pyn and automatically create tasks tied to any point in the employee lifecycle.
The ticket's already open.
Every time something significant happens in the employee lifecycle, IT needs to know about it. Someone joins — accounts need provisioning. Someone leaves — access needs revoking. Someone gets promoted — permissions need updating. And in most companies, someone in HR ends up manually pinging IT to kick all of that off.
Connect Jira to Pyn, and that handoff happens automatically.
What it does
Pyn can send an automated message to your Jira project's email address as a step inside any Flow. That message becomes a Jira ticket with employee data tokens populating the employee's name, role, team, and any other relevant details automatically.
By the time your team opens Jira, the ticket is already there.
What you can automate
Onboarding provisioning — When a new hire is enrolled, create tickets for account setup, software licenses, hardware, and system access — with the employee's name, start date, and job title already in the ticket. IT can get started without waiting for an email from HR.
Offboarding and access revocation — When a departure is recorded in your HRIS, Pyn can automatically open a ticket for IT to revoke access, disable accounts, and arrange equipment return. The same secure, consistent process every time — no chasing, no gaps.
Role changes and permission updates — A promotion or team transfer often means a change in what systems someone can access. Pyn can trigger a Jira ticket the moment a role change is recorded, so your team knows exactly what needs updating without HR having to flag it separately.
Return from leave — When an employee returns from parental leave or a sabbatical, accounts may need reactivating, access reinstating, and equipment sorting. Pyn can trigger those tickets automatically the moment the return date is reached in your HRIS.
To schedule everything for the year, and know it'll go out. It's been huge.
Claire B., People Operations at Rhino
To turn off Pyn would feel like going back to the Middle Ages.
VP People, Koala
FAQs
No. Pyn creates tickets by sending a message to your Jira project’s email address, using Jira’s own email handler. No API keys or OAuth connections are required.
Yes. Pyn tokens pull in employee data from your connected HRIS, so the task can include the new hire’s name, start date, job title, team, and more — as long as that data exists in your HRIS or ATS.
Yes. You can add multiple ticket creation steps to a single Flow, each pointing to a different Jira project email alias. One enrollment can trigger tasks for IT, Ops, and any other team simultaneously.
Yes. Any Pyn Flow can include a Jira ticket step — for offboarding, role transitions, parental leave, or any lifecycle moment that requires action from IT or Ops.
Yes. If your team uses Asana instead of or alongside Jira, Pyn can automatically create Asana tasks using the same approach.
Yes. Most teams pair Jira with their HRIS connection — which provides the employee data that determines when Flows trigger — and their Slack or Microsoft Teams connection for message delivery.
See our pricing page for current plans and details.
Get started
Connect Jira to Pyn and automatically create tickets at any lifecycle moment. No manual handoffs from HR.