Until now, sending an applicant from Hire to Journeys meant choosing from every journey in your Journeys account and filling in every field by hand, every single time. With this update, administrators decide once which journeys your hiring team can use and what information each journey needs.

Recruiters then get a ready-filled form the moment an applicant reaches the right pipeline stage, or is hired or rejected. They check it and click send. That's it.
​

Go to Settings → Integrations → Journeys. The integration now opens on a new Manage tab (the connection details have moved to a Settings tab next to it).
​

The Manage tab lists every journey from your connected Journeys account, grouped by workspace. You can:

​

**Good to know:** until you enable your first journey, everything stays as it was and recruiters can still pick any journey. As soon as one journey is enabled, only enabled journeys are offered in Hire. Fewer journeys and fewer fields means less confusion and faster sends for your team.

​

Every journey on the Manage tab has a Configure button, whether the journey is enabled or not, so you can prepare a journey before switching it on. It opens the Journeys setup panel.

​

Always-required fields. Full name and Email are always sent, so they are always in the list and marked Always required. Each must have a value before you can save. By default they are mapped to the applicant's name and email.

​

Add the fields you need. Click "Add fields" to choose from the journey's own fields and your company-wide traveller fields. Hire doesn't add fields for you, not even ones marked required in Journeys, so add exactly what this journey should collect.
​
​Note: Fields that are disabled in Journeys can't be added.
​

Required or Optional. Each added field has a Required / Optional setting. Required fields must be filled in before a recruiter can send; Optional ones can be left empty. Remove a field with the trash icon if the journey no longer needs it.

Pre-fill a field. For each field you decide what value it starts with when an applicant is added:

​

Map it to applicant data. Pick a variable such as the applicant's full name, first or last name, email, phone number or ID number, and Hire fills the field in for each applicant automatically. When you configure a journey for a specific job (see section 3), job details and answers from the application form are available as well.

In this case we are mapping the postal code from the national registry retrieved for the applicant

Leave it empty. The recruiter fills it in when sending.

Start journey when added. This toggle at the bottom of the panel decides whether the journey starts right away when an applicant is added, or waits to be started in Journeys. It's on by default, and recruiters see it preset in the send panel.

​

Click Save. The journey's "X fields · Y pre-filled" summary on the Manage tab updates immediately.

​

Each job now has a Journeys tab. It shows the journeys enabled for your company and lets you adjust them for this job only.

This tab is only viewable for users in the following roles (with access to the job):

​The journeys section in a job ad

​​Note: Only Admins + Super-admins can view and manage the company settings list
​
In this new journeys section you can:

A per-job override stays in place until you reset it, even if you remove the trigger and add it again later.
​

Company administrators also get a shortcut on this tab to the company-wide list on the Manage tab.

​

This is the part that saves the most time. On the job's pipeline, open the Journey triggers panel from the new journeys button in the toolbar (it shows a counter once triggers exist).

Trigger from a stage move

Trigger when application is marked as hired or rejected

​

The panel has two sections:
​

Adding a trigger. Click Add journey on a stage or outcome, pick a journey from the list (each card shows its description and field counts), review its configuration for this job and click Save. The journey is added when you save, so you can back out with Cancel at any point.
​

Right from the pipeline board. A stage that triggers a journey shows a green journey chip in its header. Click it to see which journey it is and what it collects, and to Edit configuration, Replace or Remove it. Stages without a trigger have an Add Journey stage trigger entry in their three-dot menu.

If a journey is later hidden for the job, disabled on the Manage tab or deleted in Journeys, its trigger is marked **Unavailable**. You can still replace or remove it, so a stage is never stuck.

​

When an applicant enters a stage that has a trigger, or is hired or rejected while an outcome trigger exists, Hire opens the Add to Journel panel automatically:

The recruiter checks the details, fills in anything that's still empty and clicks send. Closing the panel sends nothing.

​This works wherever an applicant enters a stage or receives an outcome:
​

If one move matches both a stage trigger and a hired or rejected trigger, only the outcome trigger prompts, so you never get two panels for one action.
​

The Add to Journey button on an application, on a stage's three-dot menu and in bulk actions still works exactly as before, with one improvement: it now respects your configuration. Recruiters only see the journeys available for that job and only the fields you added, with values pre-filled and the start toggle preset.
​

​

When you duplicate a job, its journey triggers and per-job journey settings come along. Stage triggers are attached to the matching stages on the new job, so the copy is ready to go without any re-setup.
​

New and duplicated jobs without triggers show a banner above the pipeline, Automate journeys from this hiring pipeline, with a shortcut to the Journey triggers panel. Dismiss it and it stays dismissed for that job.

​