1. Core Enhancements & Architecture
This general-public version is designed with modularity, white-labeling, and commercial versatility in mind. It eliminates any specific branding and integrates top-requested enterprise features:
- Dual Trigger Gateways:
- Direct Webhook Trigger: Standard
/client-onboarding-webhookpath for typical forms (Tally, Typeform, Webflow). - Stripe Checkout Trigger: Webhook listener
/stripe-checkout-webhooktuned for Stripe'scheckout.session.completedevent.
- Direct Webhook Trigger: Standard
- Agnostic Data Convergence (Process Client Details):
- A custom JavaScript code block normalizes the inputs from both Stripe sessions and form submissions. It automatically extracts Stripe checkout customer emails, splits names into first and last components, and maps custom onboarding variables passed via Stripe’s checkout session metadata.
- Multi-Database Integration Layer:
- Google Sheets Branch: Fast, spreadsheet-based data logging.
- Airtable Log Branch: Generates rich cards and relations within your CRM.
- Notion Database Page Branch: Inserts new clients directly into internal team wikis or client portals.
- Operational Switches:
- Centralized true/false toggles in the
Workflow Settingsnode allow your clients to turn integrations on or off (e.g.,enableAirtable: false,enableNotion: true) without breaking the core workflow.
- Centralized true/false toggles in the
2. Setup Instructions
A. Stripe Integration (Optional Trigger)
To trigger onboarding automatically upon a successful customer checkout:
- Point your Stripe Webhook (in the Stripe Developer Dashboard) to your n8n Stripe Trigger URL.
- Configure it to listen exclusively to the
checkout.session.completedevent. - When creating a Stripe Checkout Session via your frontend, pass the client's onboarding data as Metadata. The workflow is pre-mapped to parse these exact metadata keys:
-
company_name -
phone -
website -
success_metrics -
manual_steps -
tech_stack -
api_liability_agreement("true"/"false") -
system_access_consent("true"/"false")
-
B. Airtable Schema Configuration
Ensure your target Airtable table (e.g. "Clients") contains these fields matching your API configurations:
-
Company Name(Single Line Text) -
Contact Email(Email) -
Full Name(Single Line Text) -
Success Metrics(Long Text) -
API Waiver(Single Line Text or Single Select: Agreed / Not Agreed) -
System Consent(Single Line Text or Single Select: Agreed / Not Agreed) -
Drive Folder(URL)
C. Notion Database Properties Setup
Ensure your Notion client database has a title property and properties matching these names and types:
-
Company Name(Title) -
Email(Email) -
Representative(Rich Text) -
API Liability Waiver(Select: Agreed / Not Agreed) -
System Access Consent(Select: Agreed / Not Agreed)
D. Google Sheets Column Headers Setup
If utilizing Sheets, set up your header row exactly as:Date | Company Name | First Name | Last Name | Email | Phone | Website | Success Metrics | Manual Steps | Tech Stack | API Liability Waiver | System Access Consent | Drive Folder Link | Slack Channel Link