Automated client onboarding system with Notion, email & CRM integration
Graceful Client Onboarding Concierge — Pro
A warm, reliable onboarding system for small businesses and studios. Captures a form submission via webhook, creates a Client record in Notion, sends a concierge-style welcome email (with scheduler + optional contract link), optionally pings the owner on Telegram, mirrors the lead to Airtable/HubSpot, places a temporary Google Calendar hold, and includes a double opt-in confirmation link.
Made for: coaches, designers, boutique agencies, e-commerce and service providers who want consistent follow-up without manual busywork.
What it does (flow)
- Trigger: Form ➜
POST /client-intake(or Manual Trigger for instant demo) - Normalize & Score: Map fields, auto-generate
optInToken, computescoreandtier - Create in Notion:
Clientspage (Name, Email, Package, Notes, Status, Score, Tier, OptInToken, Consent=false) - Welcome Email: industry-tuned copy + scheduler link (+ contract link for Growth/Pro/Custom packages)
- Owner Notify (optional): Telegram ping with tier + score
- CRM Mirrors (optional): Create Airtable row and/or HubSpot contact
- Calendar Hold (optional): 30-min “Intro Hold” event (e.g., now + 48h)
- Double Opt-In:
/optin-confirm?token=...&email=...sets Consent=true & Status=Confirmed in Notion - Error Handling: On failure, send an email to the owner
flowchart TD
A[Form → Webhook /client-intake] --> B[Map Intake + Score Lead]
B --> C[Notion: Create Client]
B --> D[Build Welcome Email]
D --> E[Email: Send Welcome]
D --> F{Optional actions}
F -->|Telegram| G[Telegram: Notify Owner]
F -->|Airtable| H[Airtable: Create Row]
F -->|HubSpot| I[HubSpot: Create Contact]
F -->|Calendar Hold| J[Google Calendar: Create Hold]
K[GET /optin-confirm] --> L[Find Notion by OptInToken] --> M[Update: Consent=true, Status=Confirmed]
ER[Error Trigger] --> EH[Email Owner]
Prerequisites
- Notion database
Clientswith properties:Name (title),Email (email),Package (select),Notes (rich text),Status (select),Score (number),Tier (select),OptInToken (text),Consent (checkbox)(CSV header provided in the Sticky note on canvas.) - Email (SMTP or Gmail OAuth)
- Optional: Telegram Bot + Chat ID, Airtable (Base ID + Table), HubSpot (Contacts), Google Calendar (Calendar ID)
Configuration (Set these in Set: User Config)
NOTION_DB_ID = your Notion Clients DB ID
FROM_EMAIL = sender address for welcome email
OWNER_EMAIL = where error notifications go
SCHEDULER_URL = booking link (Calendly, Once, etc.)
BASE_URL = your public n8n domain (for opt-in link)
CONTRACT_BASE_URL = (optional) proposal/contract URL base
ENABLE_TELEGRAM = true|false
TELEGRAM_CHAT_ID = (if enabled)
ENABLE_AIRTABLE = true|false
AIRTABLE_BASE_ID = (if enabled)
AIRTABLE_TABLE = (if enabled)
ENABLE_HUBSPOT = true|false
ENABLE_CAL_HOLD = true|false
CALENDAR_ID = "primary" or calendar ID
HOLD_HOURS_FROM_NOW = number of hours (default 48)
INDUSTRY = coaching | design_studio | ecommerce | services
Credentials: Attach in node credentials panels (no secrets in JSON).
How to use
-
Import the workflow JSON.
-
Open Set: User Config and fill required values (see above).
-
Attach credentials: Notion + Email; optional Telegram/Airtable/HubSpot/Google Calendar.
-
Run Manual Trigger to simulate an intake and verify:
- Notion page created
- Welcome email received
- Optional Telegram/CRM/Calendar actions
-
Switch your form to the Production Webhook URL shown in the Client Intake Webhook node.
Sample JSON (for testing the live webhook):
{"name":"Ava Laurent","email":"ava@example.com","package":"Growth","message":"Excited to begin!"}
Double opt-in: The welcome email includes a link like
https://YOUR-N8N-DOMAIN/webhook/optin-confirm?token=...&email=...
Clicking it sets Consent=true and Status=Confirmed on the Notion record.
Industry-tuned welcome copy
Set INDUSTRY to control phrasing automatically:
coaching– gentle goals/blocks framingdesign_studio– asset handoff + milestone languageecommerce– store link + quick-win focusservices– general service language
Submission compliance
- ✅ Manual Trigger path for instant demo
- ✅ Markdown sticky notes with clear H2 sections (README, Prereqs + CSV, Setup, Testing, Compliance, Changelog)
- ✅ No hardcoded API keys (credentials only)
- ✅ Timezone-safe ISO times for calendar hold
- ✅ Clear placeholders and copy-paste CSV headers included
Troubleshooting (quick)
- No email: attach Email creds; ensure
FROM_EMAILis allowed by your provider. - No Notion page: verify
NOTION_DB_IDand property names; check Notion permissions. - Webhook issues: ensure your form sends JSON; adapt mapping for form-encoded payloads.
- Opt-in link fails:
BASE_URLmust be your public n8n domain; workflow must be active. - Calendar hold not created: set
ENABLE_CAL_HOLD=true, attach Google Calendar creds, confirmCALENDAR_ID.
Tags: onboarding, notion, email, crm, telegram, airtable, hubspot, calendar, double-opt-in, small business, concierge, women-led brands
Version: v3 (see Changelog sticky on canvas)
Automated Client Onboarding System with Notion, Email, and CRM Integration
This n8n workflow automates various steps in a client onboarding process, integrating with Airtable, Notion, HubSpot, Google Calendar, Telegram, and email. It streamlines the creation of client records, project pages, meeting schedules, and notifications, while also providing error handling.
What it does
- Starts Manually or on Error: The workflow can be triggered manually for testing or initial setup, or automatically by an error in another workflow.
- Creates Airtable Record: Initiates the onboarding process by creating a new record in Airtable, likely for a new client or project.
- Sets Data: Prepares and formats data for subsequent nodes using a "Set" node.
- Creates Notion Page: Generates a new page in Notion, presumably for the new client's project or documentation.
- Creates HubSpot Contact: Adds the new client as a contact in HubSpot CRM.
- Creates Google Calendar Event: Schedules a new event in Google Calendar, likely for an initial client meeting or onboarding session.
- Sends Welcome Email: Dispatches a welcome email to the client.
- Sends Internal Telegram Notification: Notifies an internal team via Telegram about the new client onboarding.
- Handles Errors: If an error occurs during the execution of any node, an "Error Trigger" is set up, suggesting a separate error handling workflow (not fully defined in this JSON, but indicated by the node's presence).
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Airtable Account: With appropriate API access and a base/table for client records.
- Notion Account: With API access and a database or page structure for new client projects.
- HubSpot Account: With API access to manage contacts.
- Google Calendar Account: To create calendar events.
- Email Service (SMTP): Configured for sending emails.
- Telegram Account: With a bot token and chat ID for sending notifications.
- Credentials: Configured credentials within n8n for each of the above services (Airtable, Notion, HubSpot, Google Calendar, Email (SMTP), Telegram).
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Credentials: For each node that interacts with an external service (Airtable, Notion, HubSpot, Google Calendar, Send Email, Telegram), you will need to set up or select the appropriate credentials within n8n.
- Review Node Settings:
- Airtable: Ensure the correct Base ID and Table Name are configured for creating records.
- Notion: Configure the correct database ID or parent page ID for creating new pages.
- HubSpot: Verify the contact properties being set.
- Google Calendar: Specify the calendar ID and event details.
- Send Email: Set the sender, recipient, subject, and body of the welcome email.
- Telegram: Provide the chat ID where notifications should be sent and customize the message.
- Function: Review the JavaScript code if any custom logic is applied for data transformation.
- If: Check the conditions if any conditional logic is intended (though no connections from 'If' are in the provided JSON, its presence suggests potential future branching).
- Activate the Workflow: Once all configurations are complete, activate the workflow.
- Trigger the Workflow:
- Manually: Click "Execute workflow" in the n8n editor to run it once.
- Error Trigger: If this workflow is intended as an error handling workflow, ensure it's linked to the main workflow's error settings.
This workflow provides a robust foundation for automating client onboarding, reducing manual effort and ensuring consistency across various platforms.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.