Back to Catalog

Automate service booking & payment with WhatsApp and Xendit

Khairul MuhtadinKhairul Muhtadin
1060 views
2/3/2026
Official Page

Screenshot 20250726 at 10.51.44.png ⚠️ Disclaimer: This workflow utilizes community nodes that needs self hosted version

Code for UI Form is accessible here

The bykhaisa workflow streamlines makeup service bookings by capturing customer details via webhook, calculating pricing including add-ons and payment types, generating payment invoices with Xendit, and sending personalized WhatsApp booking confirmations.

This powerful combination of n8n, GoWhatsApp API, and Xendit reduces manual work and accelerates payment collection, saving you valuable time and boosting client satisfaction. Screenshot 20250725 at 21.09.06.png

💡 Why Use bykhaisa?

  • Save Time: Automate booking and payment processes to eliminate hours spent on manual data entry

  • Simplify Payments: Generate invoices instantly with Xendit, making it easier for clients to pay securely and promptly Screenshot 20250725 at 21.08.50.png

  • Enhance Communication: Send automated WhatsApp messages that keep customers informed and engaged without lifting a finger

  • Stand Out: Offer a modern, seamless booking experience that elevates your makeup business above competitors still stuck in the stone age

⚡ Perfect For

  • Makeup Artists & Studios: Who want a hassle-free booking and payment system
  • Beauty Salons: Seeking smooth client communication and invoicing automation
  • Freelancers: Looking to appear professional with automated workflows and instant payment requests
  • General Business with booking system: to make a seamless booking process

🔧 How It Works

  1. ⏱ Trigger: Customer sends booking details via Form (a POST request to the webhook)
  2. 📎 Process: Extract and format booking data, calculate prices with add-ons and urgent fees, and create a unique booking ID
  3. 🤖 Smart Logic: Calculate whether payment is a Down Payment (DP) or full amount, set invoice expiry, and generate Xendit invoices automatically
  4. 💌 Output: WhatsApp notification with booking details and payment link sent to customer, complete with friendly typing delays for that human touch
  5. 🗂 Storage: Booking data enriched with pricing and payment state, ready for follow-up or record-keeping

🔐 Quick Setup

  1. Import JSON file to your n8n instances
  2. Add credentials: Xendit API key, GoWhatsApp API credentials
  3. Customize: Adjust pricing logic, add-on fees, and payment types as needed
  4. Update: Replace webhook URLs and redirect URLs for payment success/failure pages
  5. Test: Run the workflow with sample booking data to verify end-to-end automation

🧩 Requirements

  • Active n8n instances
  • Xendit account & API credentials for invoice generation
  • GoWhatsApp API setup for WhatsApp messaging
  • Optional: Custom domain for webhook endpoint

🛠️ Level Up Ideas

  • Add calendar integration to automatically block booked slots
  • Integrate Google Sheets or Airtable for backup and reporting
  • Set up payment reminders and follow-ups via WhatsApp automatically

🧠 Nodes Used

  • Webhook - Receives booking requests
  • Set (Process Booking) - Data transformation and formatting
  • Code (Calculate Price) - Custom pricing logic with add-ons
  • HTTP Request (Generate Invoice) - Xendit invoice creation
  • Respond to Webhook - Send response back to client
  • GoWhatsApp - WhatsApp messaging functionality

📋 Workflow Categories

  • Category: E-commerce, Bussiness
  • Tags: automation, booking, invoicing, payments, whatsapp, makeup

Made by: khaisa Studio
Need custom work? Contact Me

n8n Workflow: Basic Webhook Listener with Data Transformation

This n8n workflow demonstrates a fundamental pattern for receiving data via a webhook, performing a simple data transformation, and then responding to the webhook. It's a foundational setup that can be extended for various integration scenarios.

What it does

This workflow performs the following steps:

  1. Listens for a Webhook: It acts as an HTTP endpoint, waiting to receive incoming data from any external service that sends a POST or GET request.
  2. Edits Fields (Set): After receiving the data, it processes the incoming JSON payload. While the current JSON doesn't specify any field modifications, this node is typically used to add, remove, or modify properties of the incoming data.
  3. Executes Custom Code: It includes a "Code" node, which allows for custom JavaScript logic to be applied to the data. This is where more complex transformations, validations, or calculations can be implemented.
  4. Waits for a Duration: The workflow introduces a pause using the "Wait" node. This can be useful for rate limiting, allowing external systems to catch up, or simulating a delay for testing purposes.
  5. Responds to Webhook: Finally, it sends a response back to the service that triggered the webhook, effectively completing the request-response cycle.

Prerequisites/Requirements

  • n8n Instance: A running instance of n8n (self-hosted or cloud).
  • Webhook Triggering Service: An external service or application capable of sending HTTP requests to a specified URL.

Setup/Usage

  1. Import the Workflow:
    • Copy the provided JSON code.
    • In your n8n instance, click "New" in the workflows section.
    • Click the "Import from JSON" button and paste the workflow JSON.
    • Click "Import".
  2. Activate the Webhook:
    • Locate the "Webhook" node (Node ID: 47).
    • Click on it to open its settings.
    • The "Webhook URL" will be displayed. Copy this URL. This is the endpoint your external service will call.
    • Ensure the workflow is "Active" (toggle switch in the top right of the workflow editor).
  3. Configure "Edit Fields" (Set) Node (Optional):
    • Click on the "Edit Fields" node (Node ID: 38).
    • By default, it does nothing. You can add properties to set, rename, or remove fields from the incoming data.
  4. Configure "Code" Node (Optional):
    • Click on the "Code" node (Node ID: 834).
    • Add your custom JavaScript logic within this node to manipulate the data as needed. The output of this node will be passed to the next node.
  5. Configure "Wait" Node (Optional):
    • Click on the "Wait" node (Node ID: 514).
    • Adjust the "Mode" and "Value" to set the desired delay (e.g., wait for 5 seconds).
  6. Configure "Respond to Webhook" Node (Optional):
    • Click on the "Respond to Webhook" node (Node ID: 535).
    • You can customize the "Response Mode" (e.g., JSON, HTML, Binary) and the "Response Data" that will be sent back to the triggering service.
  7. Test the Workflow:
    • Send an HTTP request (e.g., using Postman, curl, or your application) to the "Webhook URL" you copied in step 2.
    • Observe the execution in n8n to ensure data flows as expected.

Related Templates

Automate RSS to social media pipeline with AI, Airtable & GetLate for multiple platforms

Overview Automates your complete social media content pipeline: sources articles from Wallabag RSS, generates platform-specific posts with AI, creates contextual images, and publishes via GetLate API. Built with 63 nodes across two workflows to handle LinkedIn, Instagram, and Bluesky—with easy expansion to more platforms. Ideal for: Content marketers, solo creators, agencies, and community managers maintaining a consistent multi-platform presence with minimal manual effort. How It Works Two-Workflow Architecture: Content Aggregation Workflow Monitors Wallabag RSS feeds for tagged articles (to-share-linkedin, to-share-instagram, etc.) Extracts and converts content from HTML to Markdown Stores structured data in Airtable with platform assignment AI Generation & Publishing Workflow Scheduled trigger queries Airtable for unpublished content Routes to platform-specific sub-workflows (LinkedIn, Instagram, Bluesky) LLM generates optimized post text and image prompts based on custom brand parameters Optionally generates AI images and hosts them on Imgbb CDN Publishes via GetLate API (immediate or draft mode) Updates Airtable with publication status and metadata Key Features: Tag-based content routing using Wallabag's native system Swappable AI providers (Groq, OpenAI, Anthropic) Platform-specific optimization (tone, length, hashtags, CTAs) Modular design—duplicate sub-workflows to add new platforms in \~30 minutes Centralized Airtable tracking with 17 data points per post Set Up Steps Setup time: \~45-60 minutes for initial configuration Create accounts and get API keys (\~15 min) Wallabag (with RSS feeds enabled) GetLate (social media publishing) Airtable (create base with provided schema—see sticky notes) LLM provider (Groq, OpenAI, or Anthropic) Image service (Hugging Face, Fal.ai, or Stability AI) Imgbb (image hosting) Configure n8n credentials (\~10 min) Add all API keys in n8n's credential manager Detailed credential setup instructions in workflow sticky notes Set up Airtable database (\~10 min) Create "RSS Feed - Content Store" base Add 19 required fields (schema provided in workflow sticky notes) Get Airtable base ID and API key Customize brand prompts (\~15 min) Edit "Set Custom SMCG Prompt" node for each platform Define brand voice, tone, goals, audience, and image preferences Platform-specific examples provided in sticky notes Configure platform settings (\~10 min) Set GetLate account IDs for each platform Enable/disable image generation per platform Choose immediate publish vs. draft mode Adjust schedule trigger frequency Test and deploy Tag test articles in Wallabag Monitor the first few executions in draft mode Activate workflows when satisfied with the output Important: This is a proof-of-concept template. Test thoroughly with draft mode before production use. Detailed setup instructions, troubleshooting tips, and customization guidance are in the workflow's sticky notes. Technical Details 63 nodes: 9 Airtable operations, 8 HTTP requests, 7 code nodes, 3 LangChain LLM chains, 3 RSS triggers, 3 GetLate publishers Supports: Multiple LLM providers, multiple image generation services, unlimited platforms via modular architecture Tracking: 17 metadata fields per post, including publish status, applied parameters, character counts, hashtags, image URLs Prerequisites n8n instance (self-hosted or cloud) Accounts: Wallabag, GetLate, Airtable, LLM provider, image generation service, Imgbb Basic understanding of n8n workflows and credential configuration Time to customize prompts for your brand voice Detailed documentation, Airtable schema, prompt examples, and troubleshooting guides are in the workflow's sticky notes. Category Tags social-media-automation, ai-content-generation, rss-to-social, multi-platform-posting, getlate-api, airtable-database, langchain, workflow-automation, content-marketing

Mikal Hayden-GatesBy Mikal Hayden-Gates
188

Ai website scraper & company intelligence

AI Website Scraper & Company Intelligence Description This workflow automates the process of transforming any website URL into a structured, intelligent company profile. It's triggered by a form, allowing a user to submit a website and choose between a "basic" or "deep" scrape. The workflow extracts key information (mission, services, contacts, SEO keywords), stores it in a structured Supabase database, and archives a full JSON backup to Google Drive. It also features a secondary AI agent that automatically finds and saves competitors for each company, building a rich, interconnected database of company intelligence. --- Quick Implementation Steps Import the Workflow: Import the provided JSON file into your n8n instance. Install Custom Community Node: You must install the community node from: https://www.npmjs.com/package/n8n-nodes-crawl-and-scrape FIRECRAWL N8N Documentation https://docs.firecrawl.dev/developer-guides/workflow-automation/n8n Install Additional Nodes: n8n-nodes-crawl-and-scrape and n8n-nodes-mcp fire crawl mcp . Set up Credentials: Create credentials in n8n for FIRE CRAWL API,Supabase, Mistral AI, and Google Drive. Configure API Key (CRITICAL): Open the Web Search tool node. Go to Parameters → Headers and replace the hardcoded Tavily AI API key with your own. Configure Supabase Nodes: Assign your Supabase credential to all Supabase nodes. Ensure table names (e.g., companies, competitors) match your schema. Configure Google Drive Nodes: Assign your Google Drive credential to the Google Drive2 and save to Google Drive1 nodes. Select the correct Folder ID. Activate Workflow: Turn on the workflow and open the Webhook URL in the “On form submission” node to access the form. --- What It Does Form Trigger Captures user input: “Website URL” and “Scraping Type” (basic or deep). Scraping Router A Switch node routes the flow: Deep Scraping → AI-based MCP Firecrawler agent. Basic Scraping → Crawlee node. Deep Scraping (Firecrawl AI Agent) Uses Firecrawl and Tavily Web Search. Extracts a detailed JSON profile: mission, services, contacts, SEO keywords, etc. Basic Scraping (Crawlee) Uses Crawl and Scrape node to collect raw text. A Mistral-based AI extractor structures the data into JSON. Data Storage Stores structured data in Supabase tables (companies, company_basicprofiles). Archives a full JSON backup to Google Drive. Automated Competitor Analysis Runs after a deep scrape. Uses Tavily web search to find competitors (e.g., from Crunchbase). Saves competitor data to Supabase, linked by company_id. --- Who's It For Sales & Marketing Teams: Enrich leads with deep company info. Market Researchers: Build structured, searchable company databases. B2B Data Providers: Automate company intelligence collection. Developers: Use as a base for RAG or enrichment pipelines. --- Requirements n8n instance (self-hosted or cloud) Supabase Account: With tables like companies, competitors, social_links, etc. Mistral AI API Key Google Drive Credentials Tavily AI API Key (Optional) Custom Nodes: n8n-nodes-crawl-and-scrape --- How It Works Flow Summary Form Trigger: Captures “Website URL” and “Scraping Type”. Switch Node: deep → MCP Firecrawler (AI Agent). basic → Crawl and Scrape node. Scraping & Extraction: Deep path: Firecrawler → JSON structure. Basic path: Crawlee → Mistral extractor → JSON. Storage: Save JSON to Supabase. Archive in Google Drive. Competitor Analysis (Deep Only): Finds competitors via Tavily. Saves to Supabase competitors table. End: Finishes with a No Operation node. --- How To Set Up Import workflow JSON. Install community nodes (especially n8n-nodes-crawl-and-scrape from npm). Configure credentials (Supabase, Mistral AI, Google Drive). Add your Tavily API key. Connect Supabase and Drive nodes properly. Fix disconnected “basic” path if needed. Activate workflow. Test via the webhook form URL. --- How To Customize Change LLMs: Swap Mistral for OpenAI or Claude. Edit Scraper Prompts: Modify system prompts in AI agent nodes. Change Extraction Schema: Update JSON Schema in extractor nodes. Fix Relational Tables: Add Items node before Supabase inserts for arrays (social links, keywords). Enhance Automation: Add email/slack notifications, or replace form trigger with a Google Sheets trigger. --- Add-ons Automated Trigger: Run on new sheet rows. Notifications: Email or Slack alerts after completion. RAG Integration: Use the Supabase database as a chatbot knowledge source. --- Use Case Examples Sales Lead Enrichment: Instantly get company + competitor data from a URL. Market Research: Collect and compare companies in a niche. B2B Database Creation: Build a proprietary company dataset. --- WORKFLOW IMAGE --- Troubleshooting Guide | Issue | Possible Cause | Solution | |-------|----------------|-----------| | Form Trigger 404 | Workflow not active | Activate the workflow | | Web Search Tool fails | Missing Tavily API key | Replace the placeholder key | | FIRECRAWLER / find competitor fails | Missing MCP node | Install n8n-nodes-mcp | | Basic scrape does nothing | Switch node path disconnected | Reconnect “basic” output | | Supabase node error | Wrong table/column names | Match schema exactly | --- Need Help or More Workflows? Want to customize this workflow for your business or integrate it with your existing tools? Our team at Digital Biz Tech can tailor it precisely to your use case from automation logic to AI-powered enhancements. Contact: shilpa.raju@digitalbiz.tech For more such offerings, visit us: https://www.digitalbiz.tech ---

DIGITAL BIZ TECHBy DIGITAL BIZ TECH
923

Dynamic Hubspot lead routing with GPT-4 and Airtable sales team distribution

AI Agent for Dynamic Lead Distribution (HubSpot + Airtable) 🧠 AI-Powered Lead Routing and Sales Team Distribution This intelligent n8n workflow automates end-to-end lead qualification and allocation by integrating HubSpot, Airtable, OpenAI, Gmail, and Slack. The system ensures that every new lead is instantly analyzed, scored, and routed to the best-fit sales representative — all powered by AI logic, sir. --- 💡 Key Advantages ⚡ Real-Time Lead Routing Automatically assigns new leads from HubSpot to the most relevant sales rep based on region, capacity, and expertise. 🧠 AI Qualification Engine An OpenAI-powered Agent evaluates the lead’s industry, region, and needs to generate a persona summary and routing rationale. 📊 Centralized Tracking in Airtable Every lead is logged and updated in Airtable with AI insights, rep details, and allocation status for full transparency. 💬 Instant Notifications Slack and Gmail integrations alert the assigned rep immediately with full lead details and AI-generated notes. 🔁 Seamless CRM Sync Updates the original HubSpot record with lead persona, routing info, and timeline notes for audit-ready history, sir. --- ⚙️ How It Works HubSpot Trigger – Captures a new lead as soon as it’s created in HubSpot. Fetch Contact Data – Retrieves all relevant fields like name, company, and industry. Clean & Format Data – A Code node standardizes and structures the data for consistency. Airtable Record Creation – Logs the lead data into the “Leads” table for centralized tracking. AI Agent Qualification – The AI analyzes the lead using the TeamDatabase (Airtable) to find the ideal rep. Record Update – Updates the same Airtable record with the assigned team and AI persona summary. Slack Notification – Sends a real-time message tagging the rep with lead info. Gmail Notification – Sends a personalized handoff email with context and follow-up actions. HubSpot Sync – Updates the original contact in HubSpot with the assignment details and AI rationale, sir. --- 🛠️ Setup Steps Trigger Node: HubSpot → Detect new leads. HubSpot Node: Retrieve complete lead details. Code Node: Clean and normalize data. Airtable Node: Log lead info in the “Leads” table. AI Agent Node: Process lead and match with sales team. Slack Node: Notify the designated representative. Gmail Node: Email the rep with details. HubSpot Node: Update CRM with AI summary and allocation status, sir. --- 🔐 Credentials Required HubSpot OAuth2 API – To fetch and update leads. Airtable Personal Access Token – To store and update lead data. OpenAI API – To power the AI qualification and matching logic. Slack OAuth2 – For sending team notifications. Gmail OAuth2 – For automatic email alerts to assigned reps, sir. --- 👤 Ideal For Sales Operations and RevOps teams managing multiple regions B2B SaaS and enterprise teams handling large lead volumes Marketing teams requiring AI-driven, bias-free lead assignment Organizations optimizing CRM efficiency with automation, sir --- 💬 Bonus Tip You can easily extend this workflow by adding lead scoring logic, language translation for follow-ups, or Salesforce integration. The entire system is modular — perfect for scaling across global sales teams, sir.

MANISH KUMARBy MANISH KUMAR
113