Documentation Index

Fetch the complete documentation index at: https://docs.inploi.com/llms.txt

Use this file to discover all available pages before exploring further.

​

Creating automations

Automations are designed around a hiring process you want to automate. Each automation defines when it should run, what rules should be checked, and what steps should happen after those rules are met.

​

Before you start

Start by identifying the process the automation should support. For example:

• Score applications after submission
• Update an ATS record when a candidate meets defined criteria
• Sync candidate and application data into Talent Bank
• Pause a process until a later time, then continue with the next step

You should also confirm which systems are involved, such as Studio, your ATS, Talent Bank, or an email provider.

​

Automation setup

​

1. Define the trigger

Choose what starts the automation:

• Event trigger - Starts when a candidate event happens, such as before or after an application submission is completed
• Scheduled trigger - Starts at a recurring time, such as daily or weekly

Trigger conditions can be added when an automation should only run for a subset of candidates, jobs, brands, regions, or integrations.

​

2. Add automation nodes

Nodes define what the automation does after it starts. An automation might score an application, set values used later in the automation, update an ATS application, send an email, or sync data into Talent Bank. Nodes run in sequence unless the automation branches, waits, or stops.

​

3. Add conditions and branches

Conditions route candidates through different paths based on the data available to the automation. For example, an automation can take one path when an application score is above a threshold and another path when it is below that threshold.

​

4. Add waits where timing matters

Wait steps pause the automation before the next node runs. This is useful when an action should happen after a delay, or when a later step depends on another system having time to process data.

​

5. Activate the automation

Automations can be active or paused. Active automations run when their trigger conditions are met. Paused automations remain saved but do not run.

​

Monitoring automations

Each automation run is logged. Logs help teams understand whether an automation completed, paused, or failed, and can show which step was last processed. Use automation logs to investigate:

• Missing or unexpected data from a connected system
• ATS writeback failures
• Talent Bank sync issues
• Automation rules that did not match the expected candidates or applications

​

Automation components