Send private welcome messages to new WhatsApp group members with Evolution API
Who's it for
This template is perfect for community managers, business owners, and WhatsApp group administrators who want to create a welcoming experience for new members. Whether you're running a support group, managing a business community, or moderating a hobby group, this automation ensures every new member feels valued from the moment they join.
How it works
The workflow automatically detects when someone joins your WhatsApp group and sends them a personalized welcome message directly to their private chat. It uses Evolution API to interface with WhatsApp Business and includes a natural delay to make the interaction feel more human. The entire process is hands-off once configured, ensuring consistent engagement with new members 24/7.
What it does
- Monitors group activity - Receives real-time notifications when members join or leave
- Filters for your specific group - Ensures messages are only sent for your designated group
- Validates new joins - Confirms the event is a member joining (not leaving)
- Adds natural timing - Waits a customizable period before sending the message
- Sends private welcome - Delivers your welcome message directly to the new member's chat
Requirements
- Evolution API instance (self-hosted or cloud service)
- WhatsApp Business account connected to Evolution API
- Group admin permissions for the WhatsApp group
- n8n instance (self-hosted or cloud)
How to set up
-
Import the workflow into your n8n instance
-
Configure the Set Variables node with:
- Your WhatsApp group ID (format: xxxxxxxxxxxxx@g.us)
- Evolution API key
- Instance name from Evolution API
- Evolution API URL
- Custom welcome message
- Delay time in minutes
-
Copy the webhook URL from the Webhook node
-
Configure Evolution API to send group notifications to your webhook URL
-
Test the workflow by having someone join your group
-
Activate the workflow for continuous operation
For a detailed video tutorial on setting up this workflow, check out: https://youtu.be/WO2MJoQqLvo
How to customize the workflow
- Welcome message: Edit the message in the Set Variables node to match your group's tone
- Timing: Adjust the wait time to send messages immediately or after several minutes
- Multiple groups: Duplicate the workflow and change the group ID for each group
- Rich media: Extend the HTTP Request node to send images or documents with the welcome
- Conditional messages: Add IF nodes to send different messages based on time of day or member count
- Follow-up sequence: Chain additional HTTP Request nodes to create a welcome series
n8n Workflow: Send Private Welcome Messages to New WhatsApp Group Members with Evolution API
This n8n workflow automates the process of sending personalized welcome messages to new members joining a WhatsApp group. It integrates with the Evolution API to detect new participants and delivers a private message to them, ensuring a warm and automated onboarding experience.
What it does
This workflow streamlines the welcome process for WhatsApp groups by:
- Triggering on a Webhook: It listens for incoming data, likely from a system that detects new WhatsApp group members (e.g., Evolution API webhook for group events).
- Filtering for New Participants: It checks if the incoming event signifies a new participant joining the group.
- Preparing the Welcome Message: It constructs a personalized welcome message, likely using data from the new participant event.
- Sending a Private Message: It uses the Evolution API to send this private welcome message to the new group member.
- Introducing a Delay: It includes a short delay before sending the message, which can help prevent rate limiting issues or make the message delivery feel more natural.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance (self-hosted or cloud).
- Evolution API Account: An active Evolution API account with access to WhatsApp functionalities.
- Evolution API Webhook: Your Evolution API instance should be configured to send webhooks to n8n when new members join a WhatsApp group.
- WhatsApp Group: A WhatsApp group where new members will be joining.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure the Webhook Trigger:
- Open the "Webhook" node.
- Copy the "Webhook URL". This URL needs to be configured in your Evolution API settings as the endpoint for group participant events.
- Configure the "Edit Fields" (Set) Node:
- Review the fields being set. This node is likely used to extract and format data (like the new member's number and group ID) from the incoming webhook payload. Adjust expressions as needed based on your Evolution API webhook structure.
- Configure the "Filter" Node:
- Ensure the conditions in the "Filter" node correctly identify events where a new participant has joined the group. This typically involves checking specific fields in the webhook payload (e.g.,
event.type,action,participant_added).
- Ensure the conditions in the "Filter" node correctly identify events where a new participant has joined the group. This typically involves checking specific fields in the webhook payload (e.g.,
- Configure the "HTTP Request" Node:
- This node is responsible for sending the private welcome message via the Evolution API.
- Method: Should be
POST. - URL: Set this to your Evolution API endpoint for sending messages (e.g.,
https://your-evolution-api-instance.com/message/send/text). - Headers: Add any necessary headers, such as
Authorizationwith your Evolution API key or token. - Body: Configure the JSON body to include the recipient's WhatsApp number and the welcome message text. You will likely use expressions to dynamically insert the new member's number and a personalized message.
- Example message body structure (adjust according to Evolution API documentation):
{ "number": "{{ $json.newMemberNumber }}", "text": "Hello {{ $json.newMemberName }}, welcome to our WhatsApp group! We're glad to have you here." }
- Example message body structure (adjust according to Evolution API documentation):
- Configure the "Wait" Node:
- Adjust the delay duration as desired. A few seconds (e.g., 5-10 seconds) is usually sufficient.
- Activate the Workflow: Once configured, activate the workflow in n8n.
Now, whenever a new member joins your configured WhatsApp group and your Evolution API sends a webhook to n8n, this workflow will automatically send them a private welcome message.
Related Templates
Two-way property repair management system with Google Sheets & Drive
This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.
Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API
Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen
Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack
📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.