Workflow Templates

Master Outbound WhatsApp: Baserow & WasenderAPI This workflow integrates with your Baserow 'Messages' table, triggering on 'Sent' status. Messages fire via WasenderAPI, rigorously logged as 'Outbound' in Baserow. Gain total control; drive results. How it works Monitors Baserow 'Messages' table for 'Sent' status. Sends messages via WasenderAPI. Logs outbound details in Baserow. Who's it for For teams dominating outbound WhatsApp and centralizing Baserow logging. Demand communication efficiency? This is your solution. Setup Steps Rapid implementation. Action plan: Activate all critical workflow nodes. Copy Sent_whatsapp webhook URL. Configure Baserow automation (on 'Sent' status) to trigger webhook. Ensure Baserow 'Messages' table includes 'Status' ('Sent' option), linked 'WhatsApp Number', and 'Message Content' fields. (Optional: Baserow Message Form for input). Embed WasenderAPI and Baserow API tokens in n8n Credentials. Security is non-negotiable. Requirements Active n8n instance (self-hosted/cloud). WasenderAPI.com trial/subscription. Baserow account with pre-configured 'Contacts' (link) and 'Messages' (link) tables.

This workflow triggers when a new opportunity is created in Go High Level (GHL), fetches the associated contact details, and initiates an outbound call using Vapi. The call is made by a Vapi assistant configured with the appropriate credentials. 🧾 Requirements Go High Level (GHL) A Go High Level account GHL developer private app and credentials enabled in n8n Webhook URL** from n8n added to your GHL private app Vapi A Vapi account with credit A connected phone number to make calls An assistant created and ready to make calls Your Vapi API key 🔗 Useful Links GHL Docs Vapi Docs n8n GHL Credentials Setup 🔄 Workflow Breakdown 1. Trigger: GHL Opportunity Created Triggered by a Webhook (POST) from Go High Level when a new opportunity is created. Webhook URL must be enabled in your GHL private app. 2. Get a GHL Contact Retrieves contact details from GHL CRM using the contact ID from the opportunity. Includes information such as phone number, name, and custom fields. 3. Wait 5 Minutes Introduces a short delay before making the call to avoid immediate outreach. Helps ensure data is synced and gives the system time for any follow-up automation. 4. Set Vapi Fields (Manual Step) Set the required fields for the Vapi API call: vapiPhoneNumberId – the number id making the call vapiAssistantId – the assistant who will handle the call vapiApi – your secure Vapi API key 5. Start Outbound Vapi Call Sends a POST request to https://api.vapi.ai/call Payload includes: Contact’s phone number Selected Vapi assistant Vapi phone number id to start the call ✅ Summary This n8n automation connects your CRM (Go High Level) with voice automation (Vapi) to immediately respond to new opportunities. Once a lead is created, they will receive a personalized voice call from a Vapi AI assistant. 🙋‍♂️ Need Help? Feel free to contact us at 1 Node Get instant access to a library of free resources we created.

Who it’s for? Anyone calling a Google Cloud Run service from n8n who wants a small, reusable auth layer instead of wiring tokens in every workflow. What it does / How it works This sub-workflow checks whether an incoming id_token exists and is still valid (with a 5-minute buffer). If it’s good, it reuses it. If not, it signs a short-lived JWT with your service account, exchanges it at Google’s token endpoint, and returns a fresh id_token. It also passes through service_url and an optional service_path so the caller can hit the endpoint right away. (Designed to be called via Execute Workflow from your main flow.) How to set up Add your JWT (PEM) credential using the service account private_key. In Vars, set client_email (from your key) and confirm token_uri is https://oauth2.googleapis.com/token. Call this sub-workflow with service_url (and optional service_path). Optionally include a prior id_token to enable reuse. Inputs / Outputs Inputs: id_token (optional), service_url, service_path Outputs: id_token, service_url, service_path Notes Built for loops: pair with a Merge/Split strategy to attach id_token to each item. Keep credentials in n8n Credentials (no keys in nodes). Full write-up and context: Build a Secure Google Cloud Run API, Then Call It from n8n (Free Tier) — by Marco Cassar

Tagged with: , , , ,

How It Works This sub-workflow uploads files to Dropbox and returns a direct download link: Upload file - Receives file from parent workflow and uploads to Dropbox Check for existing link - Queries Dropbox API to see if a shared link already exists for this file Create or reuse link - If no link exists, creates a new public shared link; otherwise uses existing one Convert to direct link - Transforms Dropbox's standard sharing URL (dropbox.com) into a direct download URL (dl.dropboxusercontent.com) Return URL - Outputs the final direct download link for use in other workflows Important: File names must be unique, or you'll get links to old files with the same name. **Setup Steps Time estimate: ~25-30 minutes (first time)** Create Dropbox app - Register at https://www.dropbox.com/developers/apps and get App Key + App Secret. Grant "Files and folders" + "Collaboration" permissions Configure OAuth2 credentials - Add Dropbox OAuth2 credentials in n8n (2 places: "Upload a file" and "List Shared Links" nodes). Set redirect URI to your n8n instance Create data table - Make a table called "cred-Dropbox" with columns: id (value: 1) and token (your access token) Set up token refresh - Deploy the companion "Dropbox Token Refresher" workflow (referenced but not included as its a paid workflow) to auto-refresh tokens Customize upload path - Update the path in "Upload a file" node (currently /Automate/N8N/host/) Test with form - Use the included test workflow to verify everything works Pro tip: Generate your first access token manually in the Dropbox app console to test uploads before setting up auto-refresh.

This workflow is a powerful reputation management tool designed to proactively filter customer reviews. It helps you encourage positive reviews on Google while capturing negative feedback privately before it impacts your public rating. By using an incentive, it maximizes the number of customers who enter this review funnel, giving you control over your online reputation. Who’s it for? This template is essential for any business where Google Reviews are critical: restaurants, clinics, retail stores, local services, and more. If you want to improve your Google star rating by systematically encouraging happy customers to post public reviews and addressing unhappy customers privately, this is the perfect solution. How it works / What it does The main job of this workflow is to send customers to a special review landing page. On this page, only reviews of 4 stars or more are directed to your Google Review page, while lower-rated feedback is captured in a private form. Trigger: A customer scans a QR code (e.g., in your store) and sends a message to your Telegram bot. Incentivize: The bot checks if the user is new. If so, it sends them a small discount or offer as a thank-you for their business and to encourage them to provide feedback. Send to Filter Page: After a short delay, the workflow sends a message with a link to your review filtering webpage. Track & Follow Up: The workflow tracks whether the link has been clicked (updating the status in a Google Sheet). If a user doesn't click the link after 23 hours, an automated reminder is sent to maximize engagement. How to set up Crucial Prerequisite: This workflow sends users to a review-filtering webpage. You must have this webpage already built. The page should have logic to send 4+ star reviewers to Google and capture other feedback internally. code Create a Telegram Bot: Use the BotFather on Telegram to create a bot and get your API token. Google Sheet: Create a Google Sheet with columns like: ID, First Name, Status, Feedback Message, Timestamp. Credentials: Add your Google Sheets API and Telegram Bot API credentials to n8n. Configure Nodes: In all Google Sheets nodes, select your credential and paste your Sheet ID. In all Telegram nodes, select your Telegram credential. In the "Send Review Page Link" and "Send Review Link Reminder" nodes, update the URL to point to your review filtering page. Create a QR Code: Generate a QR code for your bot's link (e.g., https://t.me/YOUR_BOT_USERNAME) and display it for your customers. Activate Workflow: Save and activate the workflow. Requirements A pre-built review filtering webpage. code An active n8n instance. Google Sheets API credentials. A Telegram Bot and its API token.

How it works This workflow automates FTP-to-Google Drive file transfers.It runs on a schedule, retrieves files in batches, downloads them from FTP, and uploads them to Google Drive while keeping original filenames.Batching ensures efficient, smooth processing without overloading the system. Step-by-step 1. Trigger and list files Schedule Trigger** – Starts the workflow at configured intervals. List Files from FTP** – Connects to the FTP server and retrieves a list of files from the target folder. 2. Batch processing setup Batch Files** – Splits files into small batches for sequential processing. 3. File handling Download File from FTP** – Downloads each file from FTP for further processing. 4. Cloud upload Upload to Google Drive** – Uploads the file to Google Drive, retaining its original name for consistency. Why use this? Eliminates manual FTP downloads and Google Drive uploads. Ensures smooth sequential processing with batch handling. Preserves original filenames for clarity and traceability. Runs automatically on a schedule, reducing human intervention. Scales easily to handle large volumes of files efficiently.

Who’s it for This workflow is designed for organizations or services managing appointments, such as interview scheduling, class enrollments, or client meetings. It’s ideal for users who want to automate appointment creation, rescheduling, cancellation, and data retrieval from a single webhook endpoint. How it works / What it does ● Receives incoming appointment requests via a Webhook node. ● Processes requests in the Set Fields node, handling multiple actions: • Set Appointment: Adds a new appointment and assigns an available interviewer. • Reschedule: Changes the appointment date based on availability. • Cancel: Deletes an appointment and frees the interviewer’s slot. • Get List: Returns a user’s list of classes. • Get User Info: Retrieves detailed information about a specific user. All actions follow strict instructions to check tables, update rows, and return structured JSON responses. How to set up Add the Webhook node and set the HTTP method to POST. Connect it to the Set Fields node. Configure the Set Fields node with the desired assignments (set_appointment, reschedule, cancel, get_list, get_user_info). Ensure your database tables (interviewers, enrollers) are properly configured and accessible. Requirements • n8n environment • Database or table access for interviewers and enrollers • Properly formatted incoming JSON requests with necessary fields (e.g., name, nationality number, preferred date). How to customize the workflow • Add or modify assignment actions to handle additional appointment scenarios. • Adjust table names or database connections based on your environment. • Extend JSON responses for custom client-side handling.

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,