Skip to content

Employee experience

Automated onboarding, triggered from Ashby

Mark a candidate Hired in Ashby and the employee syncs straight into Taito.ai — then an agent takes over the first-day setup: onboarding tasks, probation review cycle, and booked 1:1 meetings.

Join waitlist

A new hire, Sophie Lane, has just been marked Hired in Ashby and synced into Taito.ai as an employee. An agent has completed her onboarding setup: an 8-task Design onboarding list assigned, a probation review cycle scheduled to open on day 76, the first 1:1 with her manager booked, and the probation review meeting booked for day 90 — both on Google Calendar.

How it works

A first day that’s ready before it starts

Connect Ashby once. Every candidate it marks Hired syncs into Taito.ai as a new employee, which fires an Employee created trigger — running an agent that handles the tasks, review cycle, and calendar invites with no manual kickoff per hire.

Nothing dropped on day one

The setup fires the moment the hire closes — not when someone remembers to start the checklist.

The manager is ready

First 1:1 and probation review already on the calendar, the review cycle scheduled, context waiting in Taito.ai.

One source of truth

Candidate data flows from Ashby into the people graph — no retyping, no copy-paste errors between systems.

Automation 

Connect the Ashby integration, then set up onboarding automation for new employees.

When an employee is created in Taito.ai (synced from Ashby's Hired stage):
  1. Assign the onboarding task list for their department
  2. Schedule a probation review feedback cycle, opening 2 weeks before the 90-day mark

Then, via Google Calendar:
  3. Book a 30-min first 1:1 with their manager in week one
  4. Book the probation review meeting for day 90

Notify the manager and People ops when it's done.
  • Claude
  • Ashby MCP
  • Taito.ai MCP
  • Google Calendar

Frequently asked questions

What triggers the automation?
The Employee created event in Taito.ai. When a candidate reaches Ashby’s Hired stage, the Ashby integration syncs them in as a new employee — record, employment, position, and groups — which fires the trigger and runs the onboarding agent. No manual kickoff, no CSV import, no double entry.
Does the automation create the employee record?
No — that part is native. Connecting Ashby means every candidate marked Hired is synced into Taito.ai automatically, with their employment, position, job, location, and groups populated from the Ashby profile. The agent picks up from there to run onboarding.
What if different teams need different onboarding tasks?
The task list is chosen from the new hire’s department and role, so a designer and an account executive get different checklists from the same trigger.
Does it have to be Google Calendar?
The example uses Google Calendar. Any calendar with an MCP connector works the same way — the first 1:1 and the probation review are created as normal events on the manager’s calendar.

Built to work together

Keep exploring

More workflows on the Taito.ai MCP server, or browse all MCP use cases.

  • Ask HR anything, in Slack
    Employee experience

    Ask HR anything, in Slack

    Time-off balances, policy answers, headcount lookups — answered from the live record in a DM, scoped to the asker.

    • Slack
    • Claude
  • Team availability, posted to Slack every Monday
    Employee experience

    Team availability, posted to Slack every Monday

    Every Monday the Taito.ai app posts approved leave, work-from-home days, and public holidays to #general, with coverage gaps flagged.

    • Slack
  • Engineering performance reviews, grounded in Linear
    Performance

    Engineering performance reviews, grounded in Linear

    Every claim in the draft points at a real issue — shipped work, PR reviews, and cycle history pulled live from Linear.

    • Claude
    • Linear