CORTEXFLOW · FREE FOREVER

Automation

Client Onboarding Orchestrator

↓ Download workflow JSON

Import in n8n: Workflows → ⋯ → Import from file, then add your credentials. Free download with a free account.

How it works

Point your CRM, form, or checkout at one webhook and the whole onboarding happens by itself:

  1. STEP 1 — Webhook intake + log RECEIVED — a POST to /new-client (JSON: name, email, company) hits the Webhook node, reads your CONFIG — Business settings, slugifies the company name into a Slack-safe channel name, and appends a row to your Clients sheet tab with status RECEIVED.
  2. STEP 2 — Provision the client workspace — creates a Notion project page in your database, a Google Drive folder under your parent folder, and a Slack channel (client-<slug>), then posts a welcome message in the channel tagging you with links to the Notion page and Drive folder. Every provisioning node runs with onError: continueErrorOutput — any failure jumps straight to the STEP 4 alert chain.
  3. STEP 3 — Welcome email + kickoff → WELCOMED — the sheet flips to PROVISIONED, a Gmail welcome email goes to the client (what happens next, timeline, contact), the kickoff date is computed (N days out at 10:00, 45 min), a Google Calendar event is created with the client invited, and the sheet flips to WELCOMED.
  4. STEP 4 — Failure alerts + Telegram summary — if any step (Notion / Drive / Slack channel / Gmail / Calendar) fails, the owner gets a Slack alert in #general with the client name, email, and the error message, and the sheet row flips to FAILED. On the happy path, Telegram sends the 🎉 client-onboarded summary with all the links.

Status flow in Sheets: RECEIVED → PROVISIONED → WELCOMED (or FAILED)

Set up steps

You’ll need:

  • n8n (self-hosted or n8n Cloud)
  • A Notion integration — notion.so/my-account/integrations → New integration → share your client-projects database with it. The database ID is the 32-character hex in the database URL (after the last /, before any ?). Your database needs a title property named Name — the workflow only sets that one.
  • Google Drive + Google Calendar + Gmail + Google Sheets OAuth2 credentials — n8n Credentials → New → Google Drive OAuth2 API / Google Calendar OAuth2 API / Gmail OAuth2 / Google Sheets OAuth2, sign in with Google.
  • A Slack app — api.slack.com/apps → Create New App → OAuth & Permissions → add the channels:write and chat:write bot scopes → Install to Workspace → copy the Bot User OAuth Token into an n8n Slack OAuth2 API credential. (Use groups:write instead if you want private channels.)
  • A Google Sheet with a tab named exactly Clients and these headers in row 1: Date | Name | Email | Company | Notion Page | Drive Folder | Slack Channel | Status
  • A Telegram bot — message @BotFather, send /newbot, copy the token; get your chat ID from @userinfobot

Steps:

  1. Import the workflow — in n8n, Workflows → Import from File → select client-onboarding-orchestrator.json.
  2. CONFIG — Business — open the Set node and fill in:
    • notion_database_id — your Notion client-projects database ID (32-char hex from the database URL)
    • drive_parent_folder_id — the Drive folder ID from the parent folder’s URL (drive.google.com/drive/folders/<ID>)
    • slack_channel_prefix — client- by default; channels become e.g. client-acme-corp
    • owner_email — your email, used in the Slack welcome post
    • kickoff_days_ahead — 3 by default; the kickoff call lands N days out at 10:00, 45 minutes
  3. Clients sheet — create the sheet + tab + headers listed above, then in each of the four Google Sheets nodes (RECEIVED append, PROVISIONED / WELCOMED / FAILED updates) select your Google Sheets credential and pick your spreadsheet. The matching column for the updates is Email.
  4. Select credentials — Notion API in Notion — Create Project Page, Google Drive API in Drive — Create Client Folder, Slack API in both Slack nodes and the failure alert (change #general to your own alerts channel), Gmail API in Gmail — Send Welcome Email, Google Calendar API in Calendar — Create Kickoff Event (creates events on your primary calendar — change it in the node if needed).
  5. CONFIG — Notifications — paste your Telegram chat ID, select your Telegram credential, and activate the workflow.
  6. Test it — POST to the webhook URL: {"name": "Jane Doe", "email": "[email protected]", "company": "Acme Corp"} and watch the row move RECEIVED → PROVISIONED → WELCOMED.

Customize it

  • Real @mention in Slack — the welcome post and the failure alert use your email; for a true mention, hardcode your Slack user ID as <@U12345678> in the message text.
  • Private Slack channels — switch the Slack app scope to groups:write and add "isPrivate": true under the channel node’s options.
  • Different kickoff timing — change kickoff_days_ahead in CONFIG — Business, or edit the setHours(10, 0, 0, 0) line in Code — Compute Kickoff Date for a different time of day.
  • Add a contract step — insert a DocuSign / PandaDoc node between the welcome email and the kickoff event, and add a Contract column to the sheet.
  • Skip a channel — don’t need Drive folders? Delete the node and remove its reference from the Sheets PROVISIONED update — the error chain reroutes automatically.
  • CRM instead of Sheets — swap the four Sheets nodes for your CRM’s create/update nodes; the status values (RECEIVED / PROVISIONED / WELCOMED / FAILED) map 1:1 to pipeline stages.

Workflow nodes

This workflow is built from 17 nodes. Here's what each one does:

#NodeTypeWhat it does
1 Webhook — New Client Webhook Entry point — receives incoming HTTP requests that trigger the workflow.
2 CONFIG — Business Set Holds editable configuration values — fill in your own settings here before activating.
3 Code — Slugify Company Code Runs custom JavaScript to transform, filter, or compute data between steps.
4 Sheets — Log Client — RECEIVED Google Sheets Reads from or writes to a Google Sheet — this workflow's log and state store.
5 Notion — Create Project Page Notion Reads or writes pages in a Notion database.
6 Drive — Create Client Folder Google Drive Uploads, downloads, or manages files in Google Drive.
7 Slack — Create Channel Slack Posts messages or reads data in Slack.
8 Slack — Post Welcome in Channel Slack Posts messages or reads data in Slack.
9 Sheets — Update — PROVISIONED Google Sheets Reads from or writes to a Google Sheet — this workflow's log and state store.
10 Gmail — Send Welcome Email Gmail Sends or reads email through your Gmail account.
11 Code — Compute Kickoff Date Code Runs custom JavaScript to transform, filter, or compute data between steps.
12 Calendar — Create Kickoff Event Google Calendar Creates or reads events in Google Calendar.
13 Sheets — Update — WELCOMED Google Sheets Reads from or writes to a Google Sheet — this workflow's log and state store.
14 Slack — Alert Owner (Step Failed) Slack Posts messages or reads data in Slack.
15 Sheets — Update — FAILED Google Sheets Reads from or writes to a Google Sheet — this workflow's log and state store.
16 CONFIG — Notifications Set Holds editable configuration values — fill in your own settings here before activating.
17 Telegram — Client Onboarded 🎉 Telegram Sends you a Telegram message or alert.

Setup instructions

1. Add your credentials

In n8n go to Credentials → New, create each credential below, then open the named node and select it:

NodeCredential to add
Sheets — Log Client — RECEIVED Google Sheets OAuth2
Notion — Create Project Page Notion API
Drive — Create Client Folder Google Drive OAuth2
Slack — Create Channel Slack API (token)
Slack — Post Welcome in Channel Slack API (token)
Sheets — Update — PROVISIONED Google Sheets OAuth2
Gmail — Send Welcome Email Gmail OAuth2
Calendar — Create Kickoff Event Google Calendar OAuth2
Sheets — Update — WELCOMED Google Sheets OAuth2
Slack — Alert Owner (Step Failed) Slack API (token)
Sheets — Update — FAILED Google Sheets OAuth2
Telegram — Client Onboarded 🎉 Telegram Bot API

2. Fill in your config values

Open the config node listed below and replace each placeholder with your own value before activating the workflow:

NodeFieldWhat to paste
CONFIG — Business notion_database_id PASTE_YOUR_NOTION_DATABASE_ID
Your notion database id
CONFIG — Business drive_parent_folder_id PASTE_YOUR_DRIVE_FOLDER_ID
Your drive folder id
CONFIG — Business owner_email PASTE_YOUR_OWNER_EMAIL
Your owner email
CONFIG — Notifications telegram_chat_id PASTE_YOUR_TELEGRAM_CHAT_ID
Your telegram chat id

How this workflow starts

  • Webhook: Listens on path /new-client — copy the production URL from the node after activating the workflow.

Use cases

New-client onboarding is a chain of small tasks that's easy to drop a link of: the Notion project, the Drive folder, the Slack channel, the welcome email, the kickoff call. This template turns one webhook POST into the whole chain. Your CRM, form, or checkout POSTs name, email, and company to Webhook — New Client; the workflow slugifies the company name, appends a RECEIVED row to your Clients sheet, then provisions everything — a Notion project page via Notion — Create Project Page, a Google Drive folder under your parent folder via Drive — Create Client Folder, and a client-<slug> Slack channel with a welcome post tagging you. The sheet flips to PROVISIONED, Gmail sends the welcome email, Code — Compute Kickoff Date schedules the kickoff N days out at 10:00 for 45 minutes on Google Calendar, and the sheet flips to WELCOMED.

Marketing agency signing retainers weekly

A 6-person agency signs 2–3 retainers a month, and each one currently costs the founder an hour of setup busywork. Point your proposal tool or checkout at the webhook and every new client gets identical, instant setup: their client-acme-corp channel opens with links to their Notion project page and Drive folder, the welcome email lands with what-happens-next and the timeline, and the kickoff call is already on both calendars three days out. The 🎉 Telegram summary confirms the happy path; the Slack failure alert with the error message tells you exactly which step broke if something does. Practical tip: change kickoff_days_ahead in CONFIG — Business if your process is faster — a high-velocity agency might use 1 day, a strategy consultancy 5.

IT consultancy where every client needs a project space

An IT or software consultancy lives inside client workspaces — project pages, shared folders, comms channels — and inconsistency between clients creates confusion for months. This workflow makes every client space identical: same Notion page structure, same Drive folder location, same channel naming convention from the Code — Slugify Company step. Every provisioning node runs with onError: continueErrorOutput, so a Drive hiccup doesn't kill the Slack channel — the flow jumps to the STEP 4 alert chain, posts the failure to your alerts channel with the client name and error, and flips the sheet to FAILED for a clean retry. Variation: switch the Slack scope to groups:write and set isPrivate: true if client channels should be private — the welcome post and failure alerts work the same either way.

Fractional CFO, coach, or consultant with a personal process

Solo practitioners feel onboarding overhead most — there is no ops person to hand it to. For a coach with 15 active clients, the webhook can fire from a simple form on the website: the welcome email goes out with the timeline and contact details, the kickoff event lands on the primary calendar (changeable in Calendar — Create Kickoff Event), and the Clients sheet gives a one-glance pipeline of who is RECEIVED, PROVISIONED, WELCOMED, or FAILED. The Clients sheet columns — Date, Name, Email, Company, Notion Page, Drive Folder, Slack Channel, Status — become your lightweight CRM for the first 30 days of every relationship. Tip: put a true Slack @mention in the welcome post by hardcoding your user ID as <@U12345678> so new clients actually see it in the channel.

Law firm or financial practice with a contract step

Regulated practices usually need a signed engagement letter before the kickoff. The guide's customize section fits here: insert a DocuSign or PandaDoc node between the welcome email and the kickoff event, add a Contract column to the sheet, and the status flow gains a natural pause — the row stays PROVISIONED until the contract is signed. The Slack — Alert Owner (Step Failed) chain means a failed document send doesn't leave a client stranded between steps; you see the failure in #general (or your own alerts channel) with the error message and can intervene. Because the whole flow is driven by config and sheet updates, adding this step doesn't disturb the Notion/Drive/Slack provisioning that already ran.

Agency owner who wants a client list that maintains itself

Skip the CRM complexity: the four Sheets nodes (RECEIVED append, PROVISIONED, WELCOMED, FAILED updates, matched on Email) keep one Clients tab that is always current. If you outgrow Sheets, the guide notes the values map 1:1 to CRM pipeline stages, so swapping the four Sheets nodes for your CRM's create/update nodes is mechanical. Practical variation: don't need Drive folders? Delete the node and remove its reference from the PROVISIONED update — the error chain reroutes automatically and nothing else changes.

← All templates