MenuStart a projectStart

Team & operations

New starter onboarding automation

New starter onboarding automation begins when a new hire is added to BambooHR. It prepares their Google Workspace and Slack access, lists the equipment they need and books their first-week meetings, so the preparation happens before day one.

An example of how the studio would build it. No live services are connected.

From a new hire in HR to a ready first day.

  1. Step 01

    Hire recorded

    A new employee record in BambooHR provides the role, team, manager and start date.

  2. Step 02

    Accounts prepared

    Create their Google Workspace account in the right groups and queue a Slack invitation, both held until their start date.

  3. Step 03

    Kit listed

    Prepare the equipment checklist for their role and assign it to whoever orders and sets up the kit.

  4. Step 04

    First week booked

    Book the welcome, a one-to-one with their manager and team introductions into their first week.

  5. Step 05

    Team told

    Let the manager and team know in Slack who is joining, when, and what is still outstanding.

The result

New starters feel expected, not improvised.

Each role gets only the access it needs, and accounts stay inactive until the start date. A changed date or withdrawn offer updates or cancels everything prepared.

Before we connect it.

Where this is useful

Useful for growing teams where onboarding lives in one person’s head or in a checklist copied for each new starter. A sensible first version handles one role, with a person approving the access before any account is switched on.

What we need to connect

  1. 01New hire records from BambooHR with role, team, manager and start date.
  2. 02Google Workspace and Slack admin access, plus the groups and channels each role should join.
  3. 03Equipment lists, first-week meeting templates and the people responsible for each task.

What needs careful handling

Start dates move and offers are sometimes withdrawn, so key everything to the employee record and let a change update or cancel what was prepared. Only the fields each step needs should leave the HR system. Access is the sensitive part: grant the minimum for the role, keep accounts inactive until day one and record what was granted, so leaving can be as tidy as joining.

Questions people ask.

Is it safe to let an automation create accounts?

It can be, with limits. The connection can use an admin role restricted to creating users and adding groups, every action is logged, and a person can approve access before it becomes active.

Can it handle leavers too?

The same records can drive offboarding, such as suspending accounts, transferring files and recovering equipment. It is usually best built as its own workflow, with a person confirming each step.

Contract signed → Team invited
Automation 90

Signed contract to project kickoff automation

Rota published → Gaps flagged
Automation 25

Rota change notifications to calendars and WhatsApp

All automation examples