Skip to main content
A PastaHR application link is a URL that determines which flow it starts and which job the application gets linked to. Example:
The flow identifier follows the pattern ORGXXXX, where ORG is your organisation’s unique prefix (the same for all your flows) and XXXX is the individual flow identifier.
With ATS integration: if you share an application link without a remote_job_id, PastaHR cannot reliably associate the incoming application with a specific vacancy in your ATS.Without ATS integration: without remote_job_name, the application can’t be filtered by job in the applications overview. So set remote_job_name on every link.
PastaHR’s built-in Link Builder handles constructing the URL, including the correct flow identifier, the remote_job_id from your connected ATS, and any UTM parameters.
1

Navigate to the Link Builder

Click Jobs in the left sidebar, select the job posting you want to share, and click Create Link. The Link Builder opens with the ATS job ID and job name already pre-filled.
2

Select a flow and confirm the job assignment

Choose the application flow you want to use.
3

Add UTM parameters (optional)

Fill in the UTM fields for source, medium, and campaign if you want to track where applicants come from. See UTM Tracking for more information.
4

Copy and distribute the link

Click Copy Link.
After generating a link, it’s worth testing it before launching a campaign.
1

Open the link in a private/incognito window

This avoids cached sessions that could interfere with the test.
2

Verify the flow launches correctly

Confirm that the correct job title and questions appear in the conversation.
3

Check the ATS after completing a test application

Submit a test application and check that it appears under the correct vacancy in your ATS within a few minutes.
If the link opens a “job not active” message, check whether the vacancy is published and active in your ATS and whether the remote_job_id in the link exactly matches the job ID in the ATS. See the ATS Troubleshooting guide for more details on this error.