Peak Automations / Recruiting
Twenty new applications.Each with a short profile, none without an owner.
In recruiting speed matters, but not at the cost of care. Peak Automations reacts to new applications in Peak Recruit, lets an AI step create a short profile and creates tasks. Emails to candidates only go out after your approval.
Put the goal into words. Add perspectives and timing right below.
Two sample flows · Peak does not decide on candidates.
One application / one interview
Application, short profile, decision.
- Trigger
- Application in Peak Recruit or meeting outcome in Peak Booking.
- Steps
- AI summary, note, task, Gmail with approval.
- Control
- A person always makes the decisions on candidates.
Your first automation
What should happen with a new application?
Set the role, the preparation and the approval. The preview shows the rule and stores nothing.
Local working example · nothing is saved or sent. Please don't enter personal data.
Three answers. Faster screening.
Draft · not yet put together
- Trigger
- Still open
- Preparation
- Still open
- Approval
- Still open
Two recruiting moments
Where do applications pile up?
Pick the moment. The example shows what Peak prepares and what a person decides.
Open role in Peak Recruit
An application arrives in Peak Recruit.
- The action
- An AI step summarises the application along the role criteria; Peak attaches the note and creates the task “screen” for the recruiter.
- The intent
- Every application has an owner and a short profile.
Example: application → screening
- When
- Application received (example)
- Then
- AI step: summarise
- And
- Task “screen”
The example shows the structure. In Peak Automations you describe what happens with a new application.
To the next stepIs this for you?
What works today. What doesn't yet.
A recruiting team that
wants to screen faster without judging automatically.
This is where the example helps.
- Applications arrive in Peak Recruit.
- Interviews run through Peak Booking.
- Emails to candidates should be checked before sending.
Nothing runs
What Peak Automations doesn't do today.
- Peak rejects no candidates automatically and gives no score about people.
- Peak does not chase anyone on its own; every email to third parties waits for an approval.
- Triggers on inactivity or thresholds are planned, not available today.
From the example to a real automation
Build your application screening.
Describe the preparation for new applications, connect Gmail for feedback and test with a sample application.
Start with Peak AutomationsPeak Automations / Your next step
Screen fast, decide carefully.
Start with the role that gets the most applications.
See recruiting examples
For recruiting with many applications.
A person always makes the decisions on candidates.
Frequently asked questions
Are these real customer cases?
No. They are examples built from triggers and actions that exist today. We only show customer cases with evidence.
Does an automation start running right away?
No. You test it with an example first and then activate it yourself. Nothing runs before that.
Does the Agent reject applicants?
No. The Agent summarises. Who is invited or declined is decided by a person.