Note: this guide is for the Teamtailor webhooks from the integration marketplace. If you want a webhook to start a journey (as a trigger) instead, see the article Teamtailor - Automatically add candidates to a journey.
Add a webhook step to your journey that waits for something to happen in Teamtailor - for example until a candidate is moved to Hired.
Manually starting onboarding or notifying stakeholders every time a candidate moves forward quickly becomes time-consuming. With the Teamtailor integration, a journey can wait at a webhook step and continue on its own the moment a candidate is hired, reaches an interview stage, or applies. In this guide we set up the most common case: the journey waits until the candidate is hired, then continues with onboarding. The same steps work for all Teamtailor webhooks.
Which webhook should I use?
Webhook | Fires when… |
Candidate hired | a candidate is moved to their job's "Hired" stage |
Candidate moved to interview | a candidate reaches an interview stage |
Job application created | a candidate applies to a job or is added to one |
Candidate created | a new candidate is added to Teamtailor (any job, or no job) |
Job application moved | a candidate moves to any stage — for advanced setups |
Step 1 - Add the webhook to your journey
Open the journey (or create one) and click + where the journey should wait.
Choose Candidate hired under Teamtailor.
Copy the webhook URL shown in the panel - you will paste it into Teamtailor in the next step.
Step 2 - Connect it in Teamtailor
In Teamtailor, activate the Webhooks add-on if you have not already: click your profile icon, choose Add-on features, search for Webhook and click Activate.
Scroll the sidebar down until you find the Integrations section and click on Webhooks -> Create new webhook.
Give it a label you will recognize, for example Journeys - Candidate hired.
Paste the webhook URL you copied from your journey.
Under JobApplication, tick update. (For the Job application created webhook tick create instead. For Candidate created, tick create under Candidate.)
Click Save.
💡Teamtailor has no "Hired only" option here — the webhook fires on every stage move, and your journey's condition (next step) picks out the right one.
Step 3 - Tell the webhook which stage counts
Back in your journey, the webhook step asks for one thing: the Stage Name.
Type the stage name exactly as it appears in your Teamtailor pipeline - same spelling, same capital letters, no quotation marks.
⚠️ Stage names are different in every pipeline. Each job in Teamtailor has its own stages, named by whoever created the job.
The Hired stage is usually just called Hired.
Interview stages vary a lot: Interview, HR Interview, Interview 1, Entretien 1, Gespräch 1 and so on.
For a Candidate hired webhook, Hired almost always works. For Candidate moved to interview webhook, open the job's pipeline in Teamtailor first and copy the exact stage name.
💡 One journey works best for one job (or jobs sharing the same stage names). If your jobs use different stage names, copy the journey and adjust the Stage Name per copy.
Step 4 - Test it
In Teamtailor, drag a test candidate into the stage you configured (for example Hired).
Within a few seconds the journey continues past the webhook step.
If nothing happens
Check the stage name - it must match exactly: spelling, capitals, no quotes. This is the most common cause.
Check the webhook in Teamtailor points at the right URL (each webhook step has its own unique URL) and has the right event ticked.
Changed the webhook's conditions while it was already waiting? Reset the action so it picks up the new settings, then move the candidate again.
Renamed a stage in Teamtailor? Update the Stage Name in the webhook step too — it doesn't update itself.
Events are only sent for changes made after the webhook was saved in Teamtailor.