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.
Automations
Automations automate hiring processes by connecting candidate events, business rules, and follow-up actions. They help teams apply consistent logic at scale, reduce manual administration, and keep systems such as your ATS and Talent Bank up to date. Automations are built as a sequence of nodes. An automation starts with a trigger, checks any conditions, then runs each configured step in order. Steps can score applications, update records, pause until a later time, branch based on rules, or sync data into another system.What Automations are used for
- Application scoring - Evaluate submitted applications using defined criteria and store the result for review or reporting
- ATS writeback - Send automation outputs, such as scores or status updates, back to a connected ATS
- Talent Bank sync - Sync candidate, application, score, or shortlist data into Talent Bank
- Process consistency - Apply the same rules across jobs, brands, regions, or campaign types
- Operational visibility - Review automation executions and logs to understand what ran and where attention is needed
Building blocks
| Component | Description |
|---|---|
| Trigger | The event or schedule that starts the automation |
| Condition | Logic that decides whether the automation should continue or which branch should run |
| Node | An automation step, such as scoring an application, updating a record, sending an email, or syncing data |
| Wait | A pause before continuing the automation |
| Log | A record of each automation execution, including status and failure details when available |
Trigger options
Automations can start in two ways:- Event triggers - Run when something happens in the candidate journey, such as before or after an application submission is completed
- Scheduled triggers - Run on a recurring schedule, such as daily or weekly, for time-based processes
Example processes
Application scoring and ATS writeback
An automation can score an application after submission, attach the score to the inploi application record, and write relevant data back to the connected ATS. This supports teams that want consistent screening logic while keeping recruiters working in their existing ATS.Talent Bank sync
An automation can sync candidate and application data into Talent Bank after an application is completed. Additional steps can sync application scores or shortlist decisions so Talent Bank remains useful for future hiring, re-engagement, and reporting.How Automations run
When an automation is triggered, Studio evaluates any trigger conditions, then runs the configured nodes in sequence. Conditions can route candidates down different paths, wait steps can pause execution, and sync or update steps can write data into connected systems. Automation runs are logged so teams can see whether an automation completed, paused, or failed. Logs help diagnose configuration issues, integration failures, or missing data from connected systems.Creating automations
Understand the process for designing and managing automations
Triggers and node library
Learn about available triggers and automation nodes