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.