HR automation that knows your people.

Connect the HRIS you already have and set a moment up once. Pyn runs it for every employee on their own dates and follows up until it's done.

Why HR automation stalls

Your HRIS knows when someone starts, gets promoted, changes teams, or reaches an anniversary. Most of the time that knowledge stays there, and someone on the People team has to notice it and act on it.

So a patchwork fills the gap: static checklists, calendar reminders, Slack DMs sent by hand, a Notion doc nobody can find. The slowest part is the follow-up, the DM that reminds a manager to do something for their new hire. It feels like a small nuisance until you multiply it across 20 managers and 50 new hires a month.

The patchwork also has holes nobody can see. At Mindbody, a whole group of employees hired through third parties was getting no onboarding messages at all.

“Before Pyn, I didn't have a campaign for employees who were being hired through a third party. I had a huge swath of the population who was joining the company that wasn't getting onboarding messages.”

A general-purpose tool gets you halfway

The usual next step is a workflow builder, often the one IT already runs. The first flow works. Then a start date moves, a manager changes, or a policy gets a new clause, and each change is a ticket for whoever built it.

Sending the message was never the hard part. The hard part is knowing who the person is, who is around them, and which date counts. That is people data, and a general-purpose tool doesn't have it.

How an automation works in Pyn

You describe a moment once: what starts it, who is involved, and what each of them gets. From then on it runs for every person who reaches that moment.

The trigger
A change in your HRIS. Someone joins, gets promoted, changes teams, goes on leave, or leaves. Pyn also sees when someone goes from zero to one direct report, which is how it knows a first-time manager.
The timing
Each step runs off the person's own date: two weeks before they start, day one, day 90, every anniversary. Pyn checks your HRIS every hour, so when a start date moves, the steps move with it.
The people
One automation can reach the employee, their manager, their buddy, and their HR business partner, each with their own part.
The content
Vary a message by role, department, or location, and leave out the groups it doesn't apply to. An engineer in Sydney and a marketer in New York get different content from the same automation.
The sender
A Slack DM, a Microsoft Teams message, or an email, from a real person in HR, the employee's manager, or an alias such as "the People Team". Managers have learned to tune out bots. They act on a message from a person.
The steps
Messages, tasks, polls, forms, and calendar invites. A step can also hand off to another system, which is covered below.

Followed up until it's done

Put a button on a message and Pyn reminds the person, escalates to their manager, and stops the moment they act. You see who has read what and who hasn't acted, so the chasing stops being your job.

On the HRIS you already have

No rip-and-replace. Pyn reads your HRIS and acts where people already work. It works with BambooHR, HiBob, Rippling, Workday, Greenhouse, and Ashby, in Slack, Microsoft Teams, or email. See every integration.

Where Pyn sits beside n8n and Zapier

If your company already runs n8n or Zapier, "we don't need another tool" is a fair instinct. Those tools are flexible: a trigger and an action between almost any two systems. Keep them for everything that isn't about people.

HR flows are the ones that look simple until you run them at scale. A few that turn into custom builds:

  • Buddy selection that accounts for team and role and avoids repeat assignments
  • A Slack message sent on behalf of a manager or an HR business partner, not a bot
  • Onboarding cohorts where start dates differ and each session needs the right invites
  • An end-of-probation check-in that loops in the right HR business partner for that part of the org

All of this is possible in n8n. But each one is a build that someone has to own, document, and maintain as the company changes. Small policy tweaks become tickets, and the knowledge of how HR runs ends up in diagrams, not in the HR team.

A split that works

IT owns
Infrastructure and integrations. n8n or Zapier stays the automation backbone.
HR owns
People processes and their outcomes, in a system built around lifecycle moments, cohorts, and who the manager and HR business partner are.

How the two connect

Any automation in Pyn can include a webhook step. It carries the employee's name, role, team, and start date to a Zapier Catch Hook or an n8n Webhook node, and your workflow takes over: create the accounts, order the equipment, revoke access when someone leaves. Pyn supplies the moment and the data. The other tool does what comes next, and a workflow can fire back into Pyn. The details are on the Zapier, n8n, and webhooks pages.

What it costs to run both

Generic automation tools are priced on usage. Pyn doesn't charge per message sent, per task completed, or per workflow step, so more reminders and nudges don't inflate the bill. The full argument is in the business case for running Pyn alongside n8n or Zapier.

See what ran and who hasn't acted

Automations scattered across tools can't tell you which onboarding tasks are still outstanding, which managers are behind, or where a journey has stalled. Pyn keeps the tasks, messages, and actions for every moment in one place, with readership and action rates.

You can look at it two ways. The employee journey map lays every moment out across the lifecycle: what has happened, what is coming up, what is blocked, and who needs to act. The HR calendar shows the year: performance reviews, engagement surveys, holidays, and compliance cycles.

What to measure

Time back
Start with the hours recovered from manual work. In one year Carta sent more than 3,000 pre-boarding and onboarding messages to new hires. At about five minutes a message by hand, that gave one program manager 271 hours back. Read the Carta case study.
Coverage
Is every cohort being reached, in every team and location?
Follow-through
Manager response and task completion rates. Did the people around the employee do their part?
Spread
Are other teams running their own? It is one of the clearest signs the program has taken root.

“By automating support for new managers we don't have to think about it constantly. It just runs and that helps a lot.”

Where automation stops

Automation runs the logic you gave it. A trigger fires, a condition is checked, the step happens. It can't see that the laptop didn't arrive or that a new hire has gone quiet. The automation worked, and the process still broke.

It doesn't replace the relationship either. The point isn't to automate what happens between a manager and their team. It's to make sure the manager shows up for it.

And it can't interpret. An unread message might mean a technical problem, a problem with the manager, or a role that isn't what the person expected. That call stays with you.

Noticing those signals is the job AI agents are starting to take on, and they need what automation has already built: the journey, the dates, and the people. We set out the difference in AI agents vs. HR automation, and the headless processes page has where Pyn is taking it.

Start with one moment

The most common early mistake is designing the perfect journey before a single message goes out. Start smaller.

  1. Connect your HRIS.It stays the system of record. Employees don't need to download anything.
  2. Pick something you already do by hand.Julianna Kapjian-Pitt, Pyn's Director of Customer Success, asks every new customer the same question: “what have you already designed that you're still doing by hand?” Choose one with a clean trigger and a clear recipient, such as a pre-boarding message to a manager or an anniversary reminder.
  3. Run it, watch it, trust it.One automation is something you can run, watch, and trust within two weeks of going live. Then add the next.
  4. Hand the next ones to the teams that own them.Benefits runs open enrollment reminders. Talent acquisition runs interview feedback nudges. People Ops keeps the journey as a whole.

Book a demo. Bring the automation you're most afraid to touch. We rebuild it on Pyn during the call.

FAQ

Do we have to replace our HRIS?
No. Your HRIS stays the system of record. Pyn reads it and uses start dates, promotions, role changes, and tenure milestones as triggers.
How often does Pyn check for changes?
Every hour. Where the HRIS can send webhooks, as BambooHR can, a change can reach Pyn as it happens.
We already run n8n or Zapier. Why add Pyn?
Keep them for everything that isn't about people. HR flows need to know who the manager, buddy, and HR business partner are, and they change with every policy tweak. In Pyn, HR owns those flows without a ticket to IT.
Can an automation start work in other tools?
Yes. Any automation can include a webhook step that carries the employee's name, role, team, and start date to Zapier, n8n, AutomateNow, or your own systems.
What should we automate first?
Something with a clean trigger and a clear recipient. A pre-boarding message to a manager, an anniversary reminder, or a single compliance nudge are all good starting points.
Do employees need a Pyn account?
No. Messages arrive in Slack, Microsoft Teams, or email, from a colleague they know. There is nothing to download.
Does Pyn charge per message or per run?
No. Pyn doesn't charge per message sent, per task completed, or per workflow step. Pricing is per employee, and the pricing page has the details.

Your HR stack, with superpowers.

Pick the tools you need. Launch in a day. Cancel anytime.