- Filter and action steps can only be added by clicking on the ‘+’ symbol at the end of the current workflow. It is not possible to drag and drop (filter/action) steps in the middle of a workflow
- You always need to update the trigger/filter/action and save workflow, for the adjustments to be properly saved
- The workflow trigger can only be linked to 2 actions from Lever: Candidate Archive Stage Change or Candidate Hired
- It's not possible to trigger on status change (e.g. candidate moves from phone interview to onsite interview)
- It's not possible to trigger on requisition closed
- In the trigger you can only use a ‘is’ filter, in the Filter step you can also set up ‘is not’, 'contains' and 'Does not contain' filters
- The filters in starred work as AND filters, not OR filters. This means that you can’t add two Candidate Stages in the workflow since a candidate is always rejected after being in one specific candidate stage
- Filters will only work when the filters you add are spelled the exact same way as in your Lever account. To use filters in the correct way, it is really important to know all existing conditions for every field in your Lever account. logs and notifications
- When choosing the number of days delay in sending the survey, keep in mind the number of days delay used for sending your rejection emails from Lever. The delay in Starred is based on the rejection date in Lever, not based on when your rejection email is sent from Lever.
- Sender: you have options here. You can use a generic email address or create an "alias sender address". Please note: if you choose a generic email address, that address always needs to be an active user in Starred. For this reason we recommend opting for the "alias sender address" option, which you can find explained at this page.
- Custom fields:
- You can't add custom fields to received responses. For this reason, we recommend adding all custom fields before you enable your workflow. Removing custom fields from the workflow is possible at any time.
- Fields are case sensitive
- Specify custom field names without spaces (e.g JobName)
- When using the same Custom fields in multiple workflows, the notations (capital sensitive!) need to be the exact same.
Workflow A: JobName =
Workflow B: Jobname = this is wrong! Use: JobName
Updated 7 months ago