How to use a recipe
Every recipe opens with what you will build and ends with how to test it safely. In between, an automation recipe walks the trigger that starts it, the conditions that decide which records continue, and the tasks HireData runs on them. A recipe that builds one piece of content walks that content instead, question by question or block by block. Use the recipe as a starting point. Object names, stages, fields, and available tasks can differ between ATS connections, so choose the equivalent values from your own automation builder.Before you build
- Connect the app that provides the source data.
- Identify a safe test record.
- Confirm which fields and relationships are available.
- Decide who owns the outcome when a task requires human follow-up.
- Check the template gallery for an existing automation you can adapt.
- Test every external action before activating the workflow.
Available recipes
Find incomplete candidate profiles
Find profiles with missing information and route them to a recruiter, internal team, or candidate-completion workflow.
Post an outcome to your own system
Send a JSON summary to an API endpoint when a HireData event occurs, then reuse the response in later tasks.
Screen and score applicants
Build a pre-screening form that rejects the applicants who cannot do the job, ranks the rest, and summarises each response.
Ask for feedback in one click
Put a rating question in the email itself, so a candidate answers with one click from their inbox.
Build confidently
After creating a recipe:- Test the automation.
- Review its event and run.
- Confirm the result in the destination app.
- Activate it for a limited audience before expanding the conditions.