ATS integrations: Ashby and Teamtailor

Taito.ai now creates the employee record the moment a candidate reaches the hired stage in Ashby or Teamtailor, and starts the onboarding before the start date, without anyone re-typing a name. Teamtailor is an applicant tracking system (ATS), the software recruiting teams use to move a candidate from application to offer; Ashby is a recruiting platform that carries that same tracking alongside scheduling and analytics. Until now, getting a new hire out of either one and into Taito.ai has meant a CSV export or a copy-paste from the offer letter, usually done by whoever remembered to do it.

Ashby and Teamtailor

Ashby

Ashby is an all-in-one recruiting platform, where tracking, scheduling, and hiring analytics sit in the same product rather than an applicant tracker with bolt-ons added later. Its analytics module is also sold on its own to teams that keep a different tracker. Ashby, Inc. is based in San Francisco and was founded in 2018, and its plans run from teams under 100 people up through enterprise accounts over 1,000.

Teamtailor

Teamtailor is a Swedish applicant tracking system built around the career site, so the employer-branding page and the hiring pipeline are one product rather than two connected ones. The company is based in Stockholm and was founded in 2013, with offices across Europe and well beyond it. It’s best known among small and mid-market teams, though it sells into enterprise too. These two are where our customers hire today, which is why they shipped together rather than one at a time.

From hired to employee record

Both Ashby and Teamtailor expose a public API and webhooks Taito.ai connects to, though the two don’t fire the same way. Ashby ships a dedicated event for a hire; Teamtailor has no equivalent and derives the same information from a stage change on the application. The practical result is the same either way: when a candidate reaches the hired stage, Taito.ai creates the employee record with the fields the applicant tracking system already holds, name, role, start date, location, and manager, so nobody re-types what was already entered during hiring.

That record is the one time off, attendance, and documents run against from the moment it’s created, not a separate copy reconciled later. It’s the automated version of a handoff manual onboarding still has to make elsewhere in the process, and it’s the reason nobody has to remember to open a second system once a candidate accepts.

What it doesn’t set is the contract terms or the salary. Those come from the offer, not the applicant tracking system, and they’re irreversible once signed, so they stay with a person to confirm before anything goes out for signature. The integration moves the record forward; it doesn’t make the decision that record represents.

What runs before day one

From the moment the employee record exists, the same onboarding agent that runs for a manually added hire takes over:

• The welcome message, the access request, and the first-week task list, drafted and sent on schedule
• First-day and first-week tasks, planned and assigned to the right people
• A manager task, chased when it’s gone quiet
• The recurring 1:1, booked and rebooked around calendars

None of that waits for the start date. Because the record exists the moment a candidate is marked hired, the onboarding is already running before anyone’s first morning, not started as a scramble once they arrive. A new hire’s manager gets the same first-week plan and the same nudges whether the record came from a spreadsheet or from Ashby; the integration just moves the starting point earlier, closer to the offer than the desk.

If your onboarding needs a step outside the standard flow, custom agents let you describe it once and get an agent built around it. See the full flow worked through with Ashby, or browse the agents already running today.

The Ashby and Teamtailor integrations are generally available today. Connect one from the integrations settings and the next candidate you mark hired arrives as an employee.