The Automated Submission Flow is designed to eliminate the manual work required after the AI Recruiter (AIR) screens a candidate. The primary use case is the automatic creation of Submission records within your Applicant Tracking System (ATS) for candidates who meet the evaluation criteria. This capability is implemented via a Submission Node, which uses Object Write Back (OWB) functionality.
Crucially, this feature supports more than just Submissions; it can execute any supported Create API call available through the Object Write Back capability. This allows you to automatically create necessary records, such as Tasks following a candidate evaluation.
The Object Write Back functionality defines which records can initiate the creation of other records within the ATS. Here are some examples:
| Source Record | Supported Creation Targets |
| Job | Create Submission (specifically for the AIR flow) |
| Submission | Create Placement, Create Task, Create Appointment |
| Certification | Create Task |
Important Note for Admins: If a record type is not currently supported for an OWB operation, it will not appear in the UI configuration options.
Required vs. Optional Fields
When configuring the Submission or Task node, managing fields is straightforward:
- Required Fields (*): Fields that are mandatory for the ATS record creation are shown automatically in the configuration interface.
- Optional Fields: Optional fields are not displayed by default, but can be added by searching for them.
Field Value Options
You have two primary options for populating field values:
- Assign another value: This is the recommended approach for mapping data dynamically. This option lets you grab variables from workflow data or related entities, such as candidate details or job IDs from previous nodes. This ensures the created record is accurately linked and populated with contextually relevant information.
- New: This option allows you to hard-code a specific value from a list of available options for that field.
Note: We strongly recommend that before rolling out any new automated workflow widely, you thoroughly test it with a single, controlled example to ensure accurate data mapping and record creation.