N8N and Evolution API Tutorial: Create an Automated WhatsApp Group by Subscription

Transforming a WhatsApp group into a subscription product is one of the fastest and most efficient ways to monetize knowledge, build community, and generate recurring revenue. And the best part: with automation. Inspired by the theme “N8N Tutorial + Evolution API — Your WhatsApp Subscription Group 🤑”, in this article, I detail how to plan, implement, and scale a complete flow that connects payments, automatic approval, and access to a paid group on WhatsApp using n8n and Evolution API — with good business practices, retention techniques, and privacy considerations.

Video content credits: Channel Leonardo Amoyr — https://www.youtube.com/channel/UCrP0cUjPbOOowr0EF0QesMA

Why have a subscription-based WhatsApp group?

Paid groups on WhatsApp are a subscription format with a low entry barrier (everyone already uses the app) and high engagement (open rates higher than email or social media). The value delivery is direct: exclusive content, access to you/your team, networking, and support among members. When you add automation, the process becomes scalable: the customer pays, receives access automatically, is welcomed with a personalized message, and continues their value journey without friction.

• Onboarding in minutes: from purchase to access without manual intervention.
• Predictable recurring revenue with monthly/quarterly/annual plans.
• Less dependence on algorithms and more genuine relationships.
• Low operational cost with accessible tools.

What you will need

Before setting up the N8N and Evolution API flow, align your stack:

• n8n: automation orchestrator. Can be n8n Cloud or self-hosted.
• Evolution API: API layer for WhatsApp (manages sessions, groups, messages). You can self-host or use a provider.
• Payment Gateway: choose one that issues reliable webhooks (e.g., Mercado Pago, Stripe, PagSeguro, Hotmart, Kiwify, Eduzz).
• Subscriber Database: can be Google Sheets, Airtable, Notion, or a database (MySQL/Postgres). The important thing is to have status, expiration date, and phone number.
• WhatsApp Group: created in advance, with defined rules and moderation.
• Domain/SSL: if hosting n8n and the Evolution API, ensure HTTPS, security, and uptime.

Tip: want to see examples of real projects and how I apply automation and UX in practice? Check out my portfolio.

Overview of the flow

The complete flow is divided into clear steps:

1. User purchases a plan (checkout).
2. Gateway sends a webhook to n8n with the payment event.
3. n8n validates the notification signature and checks payment details.
4. If approved, n8n registers/updates the subscriber in the database (phone, name, plan, validity).
5. n8n calls the Evolution API to grant access (add to the group or send an invitation link).
6. n8n sends a welcome message, rules, and useful links.
7. Daily cron in n8n checks for renewals and delinquencies.
8. If expired, n8n removes from the group, notifies the member, and offers reactivation.

Preparing WhatsApp and the Evolution API

The Evolution API bridges your flows and WhatsApp, allowing actions like sending messages, generating invitation links, and managing participants. Some recommendations:

• Connected instance: pair via QR code, keep the device/session online and stable.
• Environment: if self-hosting, use a server with SSL, session backups, and monitoring (uptime, automatic restart).
• Keys and security: store the access token in n8n environment variables. Avoid exposing endpoints publicly without authentication.
• Compliance: respect WhatsApp policies. Avoid mass messaging, capture consent, and provide a clear opt-out for direct communications.

Important note: some actions, like “adding a participant directly”, may fail if the number is not saved, does not allow addition, or if there are platform restrictions. Robust alternative: generate a group invitation link and send it to the subscriber with instructions; it is more stable and respects user privacy.

Setting up payments and subscriptions

The heart of the model is recurring billing. When setting up your payment provider:

• Create the product/plan with defined recurrence and value.
• Activate webhooks and register your Webhook URL in n8n for events like payment approved, refunded, canceled, and renewal failure.
• Validate the webhook signature in n8n (using the provider's secret) to avoid spoofed notifications.
• Retry policy: set up automatic retries in case of card failure/expired PIX, and a grace period (e.g., 3 to 7 days) before revoking access.

If you already have a website/members on WordPress, you can integrate WooCommerce/subscription status into n8n. But it’s not mandatory: you can operate solely with a gateway + spreadsheet/DB.

Building the flow in n8n (step by step)

1) Receive and validate the payment webhook

Create a Webhook node (POST) in n8n. Upon receiving the event, validate the HMAC signature (or your gateway's mechanism) before processing. Then, extract key data: transaction ID, status, amount, name, and phone number of the payer.

2) Check payment details

Even with the webhook payload, it’s good practice to consult the provider's endpoint to confirm the status “approved/paid” and obtain metadata (plan code, frequency, next charge).

3) Normalize phone number

Standardize the number in international format (E.164). In Brazil, start with +55, area code, and number with 9 digits. This avoids failures in adding to the group and undelivered messages.

4) Register/update the subscriber

Record essential fields in your database:

• Phone (primary key)
• Name and email
• Plan, amount, frequency
• Start date and expiration date
• Status (active, pending, canceled)

If the subscriber already exists, update validity and history. This database will serve for auditing and support.

5) Grant access via Evolution API

You have two paths:

• Add directly to the group: works when allowed by WhatsApp and member settings. Useful for those who want zero friction.
• Generate group invitation link: more resilient method. Send the link to the subscriber and they join upon acceptance. The link can be temporary and periodically renewed.

My recommendation is to start with the invitation link. Besides reducing the risk of blocks, it gives control to the user and avoids adding those who do not wish to participate at that moment.

6) Welcome message + onboarding

As soon as access is granted, send a direct message on WhatsApp with:

• Welcome and a brief introduction to the value of the group.
• Group invitation link and deadline to join.
• Essential rules (conduct, schedules, support channels).
• Useful links: FAQ, account page, payment method change, cancellation.

Tip: create a clear and concise message, with a human touch. Moderated emojis help. Avoid “sounding robotic”.

7) Internal communication and CRM

Notify your team (email, Slack, Telegram) about new subscribers, renewals, failed attempts. This allows proactive contact and improves retention rates.

8) Renewal and delinquency flow

Use a daily cron node in n8n to check for subscriptions nearing expiration. For payment failures:

• Send a friendly reminder with a payment update link.
• Offer a few days of grace.
• If the failure persists, remove from the group or revoke the link and communicate with respect.

Content, moderation, and subscriber experience

A subscription group is not just access: it’s an experience. Prepare a “welcome package” and a delivery calendar.

• Pinned message with rules, FAQ, and initial resources.
• Content rhythm: for example, short daily drops, weekly live meetings, monthly summaries.
• Moderation: appoint co-admins and establish clear behavior criteria.
• Layered onboarding: in the first 7 days, guide the member to quick wins to generate an “aha moment”.
• Complementary channels: drive for materials, member area, notes in Notion — all linked.

Metrics that matter

Monitor indicators to guide decisions:

• Activation rate: paid and joined the group within 24 hours.
• Engagement: frequency of messages, participation, and responses.
• Retention and churn: percentages per cycle and reasons for cancellation.
• LTV and CAC: customer lifetime value vs acquisition cost.
• Support: time to first response, frequent topics.

With data, you decide whether to adjust pricing, content cadence, or plan benefits.

Security, privacy, and LGPD

When dealing with personal data, comply with legislation and best practices:

• Consent: make it clear that the phone will be used for subscription-related communications.
• Opt-out: make it easy to exit communications and the group.
• Minimization: collect only what is necessary (name, email, phone).
• Secure storage: protect spreadsheets/DB with access control.
• Logs and auditing: record critical events (entry, exit, failures).

Costs, pricing, and ROI

The operating cost tends to be low compared to the value delivered. For pricing, evaluate:

• Perceived value: how much the member saves/earns with your curation.
• Delivery frequency: more touchpoints justify higher tickets.
• Bonuses and community: meetings, exclusive materials, discounts.
• Plans: monthly, quarterly (with discount), annual (greater discount and bonus).

Start with a price that allows you to validate the product and gradually increase as value and demand grow.

Testing checklist before scaling

• Approved test purchase simulates the flow from start to finish.
• Webhook recognized and signature validated.
• Phone formatted correctly (+IDD, area code, number).
• Group invitation link generation ok.
• Welcome message received clearly.
• Record updated in the database with correct dates.
• Automatic removal after grace period functioning.
• Internal alerts reaching the team on failures.

Common problems and how to solve them

• QR code expires/session drops: monitor the Evolution API instance and automate reinitialization. Avoid relying on mobile; prefer stable sessions on a server.
• Does not add to the group: use the invitation link, ask to save your contact, and try again. Check if the number has an active WhatsApp.
• Pending payments: handle “pending” or “in_process” status with gentle reminders and re-sending/PIX instructions.
• Blocks and policies: maintain a reasonable message volume, avoid spam, and focus on transactional sends (onboarding, renewal, support).
• Time zones and hours: set sending windows to avoid inconveniences outside business hours.

Extensions and upgrades to your ecosystem

• WordPress site + subscriber area: centralize premium content and support.
• Segmentation within the group: tags by interest and targeted messages.
• Upsell offers: mentoring, workshops, 1:1 or VIP group.
• Email integration: communication backups and weekly newsletters.
• Automated reports: n8n sending a monthly summary of metrics.

If you want to accelerate this implementation with design, copy, and automation tailored for conversion, take a look at my portfolio and see similar projects that can serve as a reference.

Conclusion

With n8n, Evolution API, and a solid payment gateway, you build a robust system for a subscription-based WhatsApp group: the customer pays, joins, receives content, and stays engaged. The secret lies in the details — webhook validation, phone standardization, invitation link, clear onboarding, metrics, and a respectful approach to the user. Start simple, test the flow end to end, and gradually add layers of value. When executed well, this model combines proximity, recurrence, and scalability.

Now tell me: what is the biggest challenge you see in launching or scaling your subscription-based WhatsApp group — the technical part of automation, creating continuous content, or retaining members over the months?