n8n

Your workflows, triggered by real employee moments.

n8n gives your team the freedom to build automations exactly the way you want them — on your own terms, in your own environment. Pyn knows when the moments that matter happen: someone joins, gets promoted, changes teams, goes on leave, or leaves. Connect the two, and those moments become the trigger for any workflow you can build.

Connect n8n to Pyn, and every lifecycle event can set off a workflow.

What it does

Pyn can fire a webhook to n8n as a step inside any Flow. That request carries employee data tokens — the employee’s name, role, team, start date, and any other relevant details — straight into your workflow.

From there, n8n takes over. Whatever logic, branching, or integrations you’ve built runs the moment Pyn detects the event, with the employee’s data already in hand.

What you can automate

Onboarding provisioning — When a new hire is enrolled, Pyn can trigger a workflow to create accounts, order equipment, or add the employee to the right systems — with their name, start date, and job title already in the payload. The process starts without anyone in HR kicking it off.

Offboarding and access revocation — When a departure is recorded in your HRIS, Pyn can trigger a workflow to revoke access, archive accounts, or notify the right teams. The same consistent process every time — no chasing, no gaps.

Role changes and permission updates — A promotion or team transfer often means a change downstream. Pyn can trigger a workflow the moment a role change is recorded, so the right systems update without HR having to flag it separately.

Anything you can build — n8n connects to hundreds of services and lets you write custom logic in between. Any lifecycle moment in Pyn can drive whatever that workflow does next.

FAQs

How does Pyn connect to n8n?

Pyn fires a webhook as a step inside a Flow. You point that step at an n8n Webhook node, and the workflow runs whenever Pyn detects the event.

Can I include employee details like name and start date in the workflow?

Yes. Pyn tokens pull in employee data from your connected HRIS, so the webhook payload can include the employee’s name, start date, job title, team, and more — as long as that data exists in your HRIS or ATS.

Can I trigger multiple workflows from a single Flow?

Yes. You can add multiple webhook steps to a single Flow, each pointing to a different n8n workflow. One enrollment can trigger automations across several systems simultaneously.

Can I use this for automations other than onboarding?

Yes. Any Pyn Flow can include a webhook step — for offboarding, role transitions, parental leave, or any lifecycle moment that requires action in another system.

Does Pyn support other automation platforms?

Yes. The same webhook approach drives Zapier, AutomateNow, or your own systems.

Does Pyn also integrate with other tools in my employee journey?

Yes. Most teams pair n8n with their HRIS connection — which provides the employee data that determines when Flows trigger — and their Slack or Microsoft Teams connection for message delivery.