Conditions
Conditions are optional rules added to an automation to filter which applications it applies to. Without conditions, an automation applies to all applications that match the trigger. With conditions, it only applies to applications that also meet the conditions.
Why use conditions?
Triggers are broad: “when the application status changes to X”. Conditions narrow the scope: “when the application status changes to X and the application was submitted more than 30 days ago”.
Available conditions
Application Status
Checks that the application is currently in a specific custom application status.
Example: Only fire if the application status is “Under Review”.
Submission Status
Checks that the applicant’s submission status is a specific value (Submitted, Revision Requested, Revised).
Example: Only fire if the applicant has already submitted a revision.
Submitted Form Part
Checks whether a specific form part has been submitted by the applicant.
Example: Only activate the next form part if Part 1 has been submitted.
Combining conditions
Multiple conditions can be added. The setting Do all conditions need apply? decides how they are combined:
- Yes (AND): all conditions must be true for the automation to fire
- No (OR): at least one condition must be true
Start simple: most automations only need one or two conditions. More can always be added later.