Can I change the checklist without editing the workflow?

Yes. The checklist is one table at the top of the workflow: task name, owner role, day offset from the start date, and an optional note. Add, remove or re-date rows there and the next hire gets the new list. A second column supports a different checklist per department, and the guide shows the two places to change.

What if the same employee is added twice, or the record is edited after the tasks exist?

Processed employee IDs are remembered between runs, so a record picked up once is not picked up again. Edits to an existing record do not re-create tasks, because the poll asks BambooHR for inserted records only. To re-run one hire, the guide shows how to clear a single ID.

Does it create the Google Workspace or Slack accounts?

No. Account creation is a task on the checklist, assigned to IT with a due date, not something the workflow does itself. Google Workspace needs Admin SDK directory scopes for that, and Slack's SCIM API is Business+ and Enterprise Grid only. If you want that step automated, ask for a quote.

Why polling rather than a BambooHR webhook?

Both work. Polling every 15 minutes needs no public URL and no webhook configuration, which keeps setup short. If you want the tasks within a minute of the record being saved, a BambooHR webhook can post to an n8n Webhook node instead, and the guide covers that variant.

Do I need a paid n8n plan?

Any n8n works: the Cloud Starter plan or a self-hosted instance. Nothing calls in, so a self-hosted instance on a private network is fine.

BCUDrSMade to order

Hiring, onboarding & HR

BambooHR new hire → ClickUp onboarding tasks + Google Drive folder + Slack

Add the hire in BambooHR once; the checklist, the folder and the announcement follow.

Add an employee in BambooHR and the onboarding checklist starts itself. Within 15 minutes the hire has a ClickUp task list with owners and due dates counted back from the start date. A Google Drive folder holds the standard documents, copied from your templates, and the people channel carries the announcement. Built for the HR team of one at a 20-to-200-person company, where the checklist currently lives in someone's head.

How it works

B
Trigger
New employee record (BambooHR's changed-employees endpoint, polled every 15 minutes for records inserted since the last run)
BambooHR
B
Step 1
Pull the new employee's record
Fetches name, work email, job title, department, location, hire date and supervisor for each inserted employee, skips IDs the workflow has already handled, and skips records with no hire date.
if
Step 2
Build the checklist with dates
Expands the checklist table at the top of the workflow, one row per task with an owner role and a day offset, into dated tasks assigned to the IT, manager or HR person named in the settings.
CU
Step 3
Create the onboarding tasks
Creates one ClickUp task per checklist row in the onboarding list, named after the hire, with assignee, due date and the employee's BambooHR record linked in the description.
Dr
Step 4
Create the employee folder
Makes a folder named after the hire inside the HR drive, copies the template documents into it, and shares it with the manager as an editor.
S
Step 5
Announce and brief the manager
Posts the start date, role, department and manager to the people channel, and sends the manager a direct message carrying the task list and the folder link.

What changes once it runs

Every onboarding task exists in ClickUp, with an owner and a due date, within 15 minutes of the record being added in BambooHR.
IT, the manager and HR each see their own tasks, dated against the start date, in the list they already work from.
A Drive folder for the hire is created and shared with the manager before the first task is due, with the template documents already in it.
The people channel announces the start date and role on the day the record is added, not the week the person arrives.
Nobody re-types the employee's details: name, role, department, manager and start date come straight from BambooHR.

What you get

The n8n workflow export with the 15-minute poll, the checklist expansion and the four destinations wired
A starter checklist of 24 rows covering accounts, equipment, paperwork and first-week meetings, as an editable block
Setup guide covering the BambooHR API key, the ClickUp list and member IDs, the Drive template folder and the Slack app
Field-mapping sheet: BambooHR fields against the ClickUp task description and the Slack message
Recorded walkthrough of a test employee flowing from BambooHR to tasks, folder and channel
30 days of email support for setup questions

Before you start

BambooHR with API access for the user who generates the key; the key carries that user's permissions, so they need to view employee records
ClickUp on any plan, with an onboarding list and the members who will own tasks already in the workspace
A Google account with a Drive folder for HR files and a folder of template documents to copy
Slack workspace where you can install an app with the chat:write, im:write and users:read.email scopes, plus a people channel for announcements
An n8n instance, Cloud or self-hosted; no public URL is needed because the workflow polls BambooHR

Built for

Questions before you buy

Can I change the checklist without editing the workflow?: Yes. The checklist is one table at the top of the workflow: task name, owner role, day offset from the start date, and an optional note. Add, remove or re-date rows there and the next hire gets the new list. A second column supports a different checklist per department, and the guide shows the two places to change.
What if the same employee is added twice, or the record is edited after the tasks exist?: Processed employee IDs are remembered between runs, so a record picked up once is not picked up again. Edits to an existing record do not re-create tasks, because the poll asks BambooHR for inserted records only. To re-run one hire, the guide shows how to clear a single ID.
Does it create the Google Workspace or Slack accounts?: No. Account creation is a task on the checklist, assigned to IT with a due date, not something the workflow does itself. Google Workspace needs Admin SDK directory scopes for that, and Slack's SCIM API is Business+ and Enterprise Grid only. If you want that step automated, ask for a quote.
Why polling rather than a BambooHR webhook?: Both work. Polling every 15 minutes needs no public URL and no webhook configuration, which keeps setup short. If you want the tasks within a minute of the record being saved, a BambooHR webhook can post to an n8n Webhook node instead, and the guide covers that variant.
Do I need a paid n8n plan?: Any n8n works: the Cloud Starter plan or a self-hosted instance. Nothing calls in, so a self-hosted instance on a private network is fine.

Nearby on the shelf

Whole catalog