Peak Automations / Employee onboarding
The employment contract is in.The laptop isn't.
A good first day depends on many small tasks done by different people. In Peak Automations “new team member” triggers the onboarding flow: tasks for IT and the team lead with due dates, a welcome meeting in Google Calendar and a Slack message to the team. Everything runs through your workspace's connections and is switched on after a passed test run.
Put the goal into words. Add perspectives and timing right below.
Try it with a made-up team member.
Sample team member / fictional data
What a new name triggers.
- Trigger
- New team member in the workspace.
- Flow
- “Onboarding” starts: laptop, access, first week's plan.
- Welcome
- Meeting in Google Calendar, Slack message to the team.
Your onboarding in three answers
What does day one need?
Fill in the example with a made-up start. You see which details Peak needs. Nothing is saved or created.
Local working example · nothing is saved or sent. Please don't enter personal data.
Three questions. A first day without searching.
Draft · not yet put together
- The preparation
- Still open
- The people in charge
- Still open
- The welcome
- Still open
From a new name to day one
Trigger. Assign. Welcome.
The order makes sure nobody waits for access or devices on day one.
- 01Trigger
A new member is the signal.
TriggerNew team member in the workspace.
When someone joins the workspace, the automation starts once for that person.
New member → run - 02Assign
The flow creates the tasks.
Flow“Onboarding” starts: laptop, access, first week's plan.
“Start a flow” assigns the steps of your onboarding plan with due dates to IT and the team lead.
Flow → tasks - 03Welcome
Meeting and message are set.
WelcomeMeeting in Google Calendar, Slack message to the team.
A welcome meeting in the connected Google Calendar and a Slack message to the team.
Sample artifact → welcome meeting
The next proof is the product
Prepare the next first day.
In Peak Automations you pick the trigger “new team member”, set flow, tasks, meeting and message, and switch on after the test run.
Start with Peak AutomationsPeak Automations / Your next step
Day one starts before day one.
Try the example with the next start in your team.
See the onboarding example
Welcome, everything is ready.
Meeting in Google Calendar, Slack message to the team.
Frequently asked questions
What triggers onboarding?
The trigger “new team member”, when someone joins the workspace.
Does Peak create accounts in Slack or Google?
No. Peak creates tasks for it; a person sets up the accounts.
Where does the onboarding plan come from?
From a flow in your workspace that the automation begins with “start a flow”.