Triggers and node library
Automations are made from a trigger and a sequence of nodes. The trigger decides when the automation starts. Nodes define what happens next, including logic, scoring, data updates, communication, and sync steps.Triggers
Automations can start from an event or a schedule.
Event triggers can run before or after an application submission is completed. Scheduled triggers use a recurring schedule, such as daily or weekly.
Node library
Control flow
Use control flow nodes to decide how the automation should move between steps.Application intelligence
Use application intelligence nodes to evaluate applications and enrich automation decisions.Data shaping
Use data shaping nodes to prepare values for later steps.Communication
Use communication nodes to send messages as part of the automation.ATS and application updates
Use update nodes to write automation outputs back to application records.Talent Bank
Use Talent Bank nodes to keep candidate and application data available for future hiring. See syncing from Automations for how to order these nodes.Some nodes depend on connected systems, such as an ATS integration or Talent Bank configuration. Availability may vary by customer setup.