Automate Client Onboarding With n8n: Welcome Email, Notion, and More

Signing a new client should feel like a win, but the first 20 minutes after that signature are always the same frantic routine: write the welcome email, create the project folder, add them to the CRM sheet, send the intake form, put the kickoff call in the calendar. n8n client onboarding automation runs that entire routine in under 30 seconds, the moment the client signs, every time.

The symptom is familiar: you're mid-focus on actual client work, your phone buzzes with a payment notification, and suddenly you're context-switching into a copy-paste checklist. Miss a step and the new client's first impression is silence for 30 minutes. Nail every step and it still cost you 20 minutes of focused time.

I run this on n8n self-hosted on a 5-dollar-per-month VPS. When a client signs, the first thing they receive is a personalised email referencing exactly what they purchased and their next three steps, written by Claude in under 10 seconds. The Notion project page exists before the kickoff call. I usually find out a client signed by seeing the Slack notification from the workflow, not by checking my inbox.

One client replied "wow, how did you send this so quickly?" two minutes after checkout. I had not even opened my email yet.

What does an automated client onboarding workflow actually do?#

The n8n client onboarding automation runs five actions the moment a trigger fires: it generates a personalised welcome email with Claude, sends it via Gmail, creates a Notion project page, posts a Slack or Telegram notification to you, and logs the client in a Google Sheets CRM. The whole sequence finishes in under 30 seconds.

The architecture is a spine with optional arms. The spine is always: Trigger -> Set node -> AI Chain -> Gmail Send. The arms are Notion, Slack or Telegram, and Sheets. Build only the spine if you want results today and add arms later.

Every task done faster and more consistently by the workflow.

Here is the starkest way to see the difference this makes:

Twenty minutes of interrupted work versus 30 seconds of automatic execution, with no quality variation. Claude writes the same calibre of email at 3am on a Sunday as it does on a Monday morning.

Which trigger should you use?#

Use the trigger that matches how you already collect client information. Stripe is right if you take payment before onboarding. Typeform works when the intake form is the entry point. Google Sheets fits when clients come through a Google Form or a manually updated sheet. All three feed the same downstream workflow after the Set node normalises them.

Stripe Webhook: Add a Webhook node in n8n with a POST method. Register the endpoint in the Stripe Dashboard under Developers -> Webhooks, listening for the customer.created event. The payload includes customer.name, customer.email, and any metadata fields you configure, such as the service name.

Typeform Trigger: Add the Typeform Trigger node. It maps every form field by label, so What service are you signing up for? becomes a usable field. See the n8n Typeform Trigger docs for authentication steps.

Google Sheets Trigger: Add the Google Sheets Trigger node set to Row Added. This pairs well with Google Forms, which auto-append submissions to a linked sheet. See the n8n Google Sheets Trigger docs.

After whichever trigger you choose, add a Set node. Create exactly four output fields: clientName, clientEmail, serviceBooked, notes. Map them from the trigger's field names. Every node after this point uses those four fields and has no idea which trigger fired.

The structural insight worth internalising: swap the trigger, keep the logic.

If you are already running a lead follow-up sequence before onboarding, see the solopreneur lead follow-up automation for how to chain that into this workflow.

How does Claude write the personalised welcome email?#

Claude reads the client's name, the specific service they booked, and any notes from the intake form, then writes a warm 3-sentence welcome paragraph and a numbered list of next steps. This is not a mail-merge template with {{first_name}} swapped in. The output reads like a person wrote it, because the model reasons about context rather than filling blanks.

In n8n, add a Basic LLM Chain node (simpler than the AI Agent node when you do not need tool calls). Connect it to Anthropic using your API key. As of mid-2026, the available models include Claude Opus 4.8, Sonnet 4.6, and Haiku 4.5 (Anthropic model overview). Haiku 4.5 is fast and cheap enough for this task; use Sonnet 4.6 if you want richer prose.

Here is the prompt template to paste into the node:

You are a friendly business assistant. Write a welcome email body for a new client.

Client name: {{ $('Set').item.json.clientName }}
Service booked: {{ $('Set').item.json.serviceBooked }}
Intake notes: {{ $('Set').item.json.notes }}

Write:
1. A warm 3-sentence welcome paragraph that references their name and the specific service.
2. A numbered list of their next three steps (schedule kickoff call, complete intake form, review the project brief).

Keep the tone conversational and professional. Do not use greetings like "Dear" or sign-offs.

Example input: clientName: Sarah Chen, serviceBooked: Brand Strategy Sprint, notes: Launching a DTC food brand, needs positioning before October.

Example Claude output:

Sarah, welcome to the Brand Strategy Sprint. I'm looking forward to helping you build sharp positioning for your food brand before the October launch. You've picked exactly the right moment to get this locked in before go-to-market.

Your next three steps:

1. Schedule your kickoff call using the link below.
2. Complete the brand intake questionnaire (takes about 15 minutes).
3. Review the Sprint brief I'll send once we've spoken.

That output goes directly into the Gmail node body. No editing required.

Five clients recoup the 90-minute setup completely.

How do you build the full workflow in n8n?#

Building the n8n client onboarding automation takes about 90 minutes the first time. After that, every new client runs through it automatically in under 30 seconds. The steps below cover the full spine (trigger, Set node, AI, Gmail) plus all three optional arms: Notion, Telegram, and the Sheets CRM log.

Build each step in order; Notion and Sheets are optional arms.

Step 1: Trigger node#

Add your chosen trigger (Stripe Webhook, Typeform Trigger, or Google Sheets Trigger) as node 1. Configure authentication and register the webhook URL in the external platform.

Step 2: Set node#

Add a Set node. Create the four fields: clientName, clientEmail, serviceBooked, notes. Save and connect it to the trigger.

Step 3: AI Chain node#

Add a Basic LLM Chain node (n8n LangChain docs). Select Anthropic as the provider, choose Claude Haiku 4.5, and paste the prompt template from the section above.

Step 4: Gmail Send node#

Add a Gmail node, operation Send (n8n Gmail docs). Set:

• To: {{ $('Set').item.json.clientEmail }}
• Subject: Welcome to your {{ $('Set').item.json.serviceBooked }}, {{ $('Set').item.json.clientName }}
• Message: the output from the AI Chain node
• Enable HTML if you want formatted bullet points.

Add an error branch on this node. If anything downstream fails, the welcome email must still go out.

Step 5: Notion Create Page node#

Add a Notion node, operation Create Page (n8n Notion docs). Set Parent to your Clients database. Map: Name = clientName, Email = clientEmail, Service = serviceBooked, Status = Active.

Step 6: Telegram or Slack notification#

Add a Telegram node (Send Message) or a Slack node (n8n Slack docs). Use this message:

New client signed: {{ $('Set').item.json.clientName }}
Service: {{ $('Set').item.json.serviceBooked }}
Email: {{ $('Set').item.json.clientEmail }}

Step 7: Google Sheets CRM log#

Add a Google Sheets node, operation Append Row (n8n Sheets docs). Columns: Date, Name, Email, Service, Source. This creates a single running record of every client. For a deeper look at using Sheets as a lightweight CRM backend, see Google Sheets as a database with n8n.

What if Notion fails during the workflow?#

Add an error branch on the Notion node and the welcome email goes out regardless of what Notion or Sheets returns. Without an error branch, a Notion API error halts the entire execution at that node and the client never receives the welcome message, which defeats the purpose of the automation.

In n8n, open the Notion node settings and enable the Error Branch option (n8n error handling docs). Connect the error output to a Telegram notification that alerts you to the failure. You can then create the Notion page manually in the rare case it fails, while the client experience stays clean.

The design principle: decouple the client-facing action (the email) from the internal actions (Notion, Sheets). The client never needs to know about your project management system.

For a complete guide to building reliable error branches across any n8n workflow, see n8n error handling for reliable workflows.

An error branch keeps the email going out even if Notion fails.

What should you add next?#

Once the core spine runs cleanly, adding more arms is straightforward: each one plugs into the existing flow without restructuring the nodes already working. The three highest-value additions are a Calendly link in the welcome email, a contract-signing node via DocuSign, and an intake questionnaire trigger via Typeform.

Calendly or Cal.com link in the email: Add the booking URL to the Claude prompt so it appears as step one in the client's next-steps list. No extra node needed.

Contract signing via DocuSign: Add a DocuSign node after the Gmail send. Pass the client email and a pre-built contract template ID. The client receives the welcome email and the contract link within the same 30-second window.

Intake questionnaire via Typeform: If your trigger is Stripe, the client has paid but not filled out an intake form yet. Add a Typeform link to the Claude-generated email as step two. The workflow handles it automatically.

Reading and sorting incoming replies: Once clients reply to the welcome email, you need a way to triage those messages without opening every one. The Claude email triage agent for n8n shows how to route incoming mail automatically.

The break-even math is simple: 20 minutes of manual onboarding per client, multiplied by five clients, equals 100 minutes of recovered time. The workflow takes about 90 minutes to build. After client five, every minute is pure gain.

Build the spine first (Trigger, Set, AI Chain, Gmail). Run it with three dummy entries and verify the emails read naturally. Then add the Notion arm, the Slack notification, and the Sheets log one node at a time. Each arm takes under 10 minutes once the spine works.

Once onboarding runs itself, the next question is what to build next: these n8n automation ideas are eight AI workflows worth wiring up.