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 workflows
Workflows are designed around a hiring process you want to automate. Each workflow 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 workflow 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
Workflow setup
1. Define the trigger
Choose what starts the workflow:- 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
2. Add workflow nodes
Nodes define what the workflow does after it starts. A workflow might score an application, set values used later in the workflow, update an ATS application, send an email, or sync data into Talent Bank. Nodes run in sequence unless the workflow branches, waits, or stops.3. Add conditions and branches
Conditions route candidates through different paths based on the data available to the workflow. For example, a workflow 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 workflow 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 workflow
Workflows can be active or paused. Active workflows run when their trigger conditions are met. Paused workflows remain saved but do not run.Monitoring workflows
Each workflow run is logged. Logs help teams understand whether a workflow completed, paused, or failed, and can show which step was last processed. Use workflow logs to investigate:- Missing or unexpected data from a connected system
- ATS writeback failures
- Talent Bank sync issues
- Workflow rules that did not match the expected candidates or applications
Workflow components
| Component | Description |
|---|---|
| Trigger | The event or schedule that starts the workflow |
| Node | A step that performs work, such as scoring, updating, syncing, or sending data |
| Condition | Logic that controls whether the workflow continues or which branch runs |
| Wait | A pause before the workflow continues |
| Log | A record of the workflow run and its outcome |