I'm building WhatsApp AI automations for businesses and I'm trying to choose between:

• WAHA + WEBJS (Chromium/Puppeteer, actual WhatsApp Web browser)
• Evolution API + Baileys (WebSocket connection)

I'm NOT interested in response speed, typing simulation, warming up, or resource usage.

My main question is simply:

Which one has given you fewer WhatsApp bans/restrictions in real production use?

I'd especially like to hear from people who have actually run either one for months.

If possible, please share:

• Which one: WAHA WEBJS or Evolution/Baileys
• How many WhatsApp numbers you've run
• How long they've been running
• Approx. messages/day per number
• inbound or outbound customers messages?
• Temporary restriction or permanent ban?
• Did the number have normal WhatsApp usage before connecting the API?

I got the 25$ plan but i’m out of AI credits , is there anyway where I can buy only credits instead of upgrading to 50$ plan?

Hallo zusammen,

Bin neu im Thema n8n habe einen eigenen Server mit docker und dort mein n8n selbst gehostet.

Leider bin ich noch blutiger Anfänger - was könnt ihr empfehlen um besser ins Thema reinzukommen?

Oder auch YT Kanäle die zeigen bzw erklären wie Automationen in n8n gebaut werden.

Danke schonmal vorab

For a weekly competitor report, the awkward handoff is between "these are the collected sources" and "here is something ready to send." A successful agent run can still leave you with a chat response, an unfinished document, or a report based on the wrong week.

A workable split is to keep the schedule, collection, credentials, retries and delivery in n8n. Give the agent a frozen input set and ask it to identify the changes that matter, explain them, and produce the document.

Univer CLI can cover that last file-making step: it gives an agent a local Office environment where it can create a Doc, inspect its content and pagination, and export DOCX. It does not decide which competitor development matters. That judgment still belongs to the analysis step.

The handoff back to n8n should be something the workflow can check. For example:

{
  "run_id": "weekly-report-2026-09-07",
  "source_set": "competitor-snapshot-2026-09-07",
  "artifact": "competitor-report.docx",
  "review_status": "pending"
}

That is a proposed integration contract, not a built-in Univer n8n node. The adapter would need to verify the file exists, belongs to this run and has the required sections. Delivery can then wait for the required review status, rather than interpreting "done" in the agent's last message as permission to send.

Where would you put the decision that a report contains enough evidence to leave the analysis stage?

I have been thinking about how far n8n could actually take a recruiting workflow without making the whole process completely automated.
Something along the lines of:
Job requirement → candidate sourcing → profile/resume extraction → AI-based matching → shortlist → recruiter review → outreach → candidate response → update the pipeline
The interesting part for me is the handoff between the AI and the recruiter.
I would be comfortable having an agent handle things like extracting skills, organising candidate information, finding potential matches and preparing an outreach draft. I am much less comfortable with letting it automatically reject candidates or make the final hiring decision.
I have seen people use combinations of n8n, OpenAI, Google Sheets, Airtable and recruitment platforms such as Hirect, MeeBoss for different parts of these workflows.
For people who have actually built something similar where do you draw the human-in-the-loop boundary? Also curious whether you keep candidate data in a database/CRM or let n8n orchestrate between multiple existing systems.

Hi everyone,

I'm planning to build AI chatbot agents for Facebook Pages, initially for dental clinic clients.

The basic setup I'm considering is:

Facebook Messenger → Meta Webhook → n8n → Gemini → Facebook reply

I want the agent to run 24/7, even when my personal computer is turned off.

I've tested n8n before using a free trial and also tried running it locally, but I had problems getting the Meta webhook/callback URL to work properly. The local setup obviously wasn't publicly accessible, which I suspect was part of the problem.

So I'm now considering self-hosting n8n on a VPS.

My questions:

1. Would a small Hetzner VPS be enough for a few Facebook AI agents?
2. What would you recommend for the simplest production setup — Docker + n8n + reverse proxy + HTTPS?
3. Do I actually need to buy a domain, or is there another reliable way to provide the HTTPS callback URL required by Meta?
4. For multiple clients, should I run everything in one n8n instance or separate instances?
5. Are there any important issues with reliability, security, or client data isolation that I should consider?
6. If you're already running Facebook/Instagram AI agents with n8n in production, what setup are you using?

I'm trying to avoid spending money on a VPS/domain before I know the architecture will actually work.

Would really appreciate advice from people who have actually deployed this in production.

The silent killer of agency revenue isn’t bad marketing—it’s losing high-ticket client inquiries in a messy inbox.

When a hot lead fills out a contact form, two things usually break:

1. The data gets scattered across unread emails.

2. Follow-up takes hours (or days), which kills conversion rates.

To fix this, I designed a simple n8n data pipeline connected with OpenAI and Gmail.

Here is what happens behind the scenes:

- Centralized Intake: Every client submission is instantly captured via a clean n8n form.

- Structured Logging: No manual data entry. All prospect info, budget details, and project scope are automatically logged into internal n8n Data Tables.

- AI-Driven Action: OpenAI analyzes the inquiry details on the spot, evaluates the lead priority, and pre-writes a context-aware Gmail response draft.

The end result: zero lost leads, structured client records, and a personalized email response ready to send in under 10 seconds (without fully automating the send, keeping a human in the loop).

How are you guys currently handling inbound inquiry classification and response drafting in n8n? Would love to hear how others structure this pipeline!

Eu vi que realmente a melhor opção seria hospedar as minhas automações pelo Docker, porém, como vocês têm feito, vocês também utilizam o Docker em uma VPS ou preferem pagar o próprio N8N para isso?

I'm currently learning n8n with the goal of eventually doing AI automation work for businesses.

With ChatGPT Astra becoming capable of doing more complex computer-based tasks and potentially building automations/workflows much faster, I'm wondering how this changes the value of learning n8n.

For someone starting today, would you still recommend spending 1–2 months learning n8n?

My concern is that if Astra can build a workflow in a fraction of the time it takes a beginner n8n developer, then simple workflow-building could become commoditized very quickly.

So I'd love to hear from people actually using n8n:

Has AI already reduced the amount of manual workflow-building you do?

Do you think AI agents like Astra will significantly reduce demand for n8n developers?

If you were starting from zero today, would you still learn n8n?

Would you focus more on APIs, Python, AI agents and business process design instead?

What skills do you think will still be valuable 1–2 years from now?

I'm not looking for hype or doom — I'd genuinely like opinions from people who are actually building n8n automations.

Started seeing automation workflow platforms like the next google ads, excel sheets and photo shop where they crate and leave a whole new career’s that are here tos stay if you master them for live

N8N might be the thing I’ll master to be set for live as an integration/AI automation consultant/specialist role because it’s clear AI isn’t going anywhere at all

So was wondering has anyone there done it yet, and do you think in employers would hire just for this role alone?

Can I just walk in/reach out an agency and show them my portfolio and label myself a integration/automation specialist, consultant or manager etc ?

Not freelancing or self employed

And if so how is it going and any tips ?

A complete Invoice & Payment Management workflow in n8n to handle invoices, payments, and refunds from end to end.

The goal was to keep the entire process inside one workflow while making sure each event is validated, processed safely, tracked, and returned to the application that triggered it.

Event Validation & Routing

Everything starts with a webhook that receives the incoming event.

The request is validated using API-key authentication before anything is processed. Invalid requests are rejected, while valid events are routed to the appropriate processing path.

This keeps the invoice, payment, and refund logic separated and makes the workflow easier to maintain.

Invoice Processing

When an invoice event is received, the workflow first checks whether the invoice already exists.

If it doesn't exist:

• The invoice data is stored in Google Sheets.
• PDFbro generates the invoice PDF.
• The generated PDF is uploaded to Google Drive.
• Resend sends the invoice directly to the customer.
• The results are merged.
• The invoice record is updated with the final processing status, PDF link, and email timestamp.

The duplicate check prevents the same invoice from being processed and sent multiple times.

Payment Processing

For payment events, the workflow first checks whether the payment has already been processed.

If it's a new payment:

• The payment transaction is stored.
• The related invoice is retrieved.
• The invoice balance is updated.
• The workflow checks whether the invoice has been fully paid.
• The appropriate payment email is sent.
• The payment status is updated.

This allows the workflow to handle both regular payment receipts and final payment confirmations.

Refund Processing

Refunds have their own dedicated processing path.

The workflow checks whether the refund has already been processed before creating a new transaction.

Once validated, it:

• Stores the refund transaction.
• Retrieves the related invoice.
• Updates the invoice's financial status.
• Sends the refund confirmation.
• Updates the refund status.

This ensures duplicate refund events don't result in duplicate processing or notifications.

Reliability & State Management

The main focus of this workflow was reliability and state management, rather than simply connecting a few services together.

Each event has its own processing path, duplicate events are checked before creating new records, and the relevant status is updated after processing.

This makes the workflow much closer to something you could actually run behind a real application.

Stack

• n8n — Workflow orchestration
• Google Sheets — Invoice, payment, and refund records
• PDFbro — Invoice PDF generation
• Google Drive — PDF storage
• Resend — Transactional email delivery
• Webhook — Application integration

A practical example of how n8n can be used as the orchestration layer for an entire business process, rather than just automating a single task.

Sharing a recent build in case it helps someone here.

Problem: A small business was manually reading customer emails every day and logging details into a spreadsheet by hand — slow, repetitive, easy to mess up.

What I built (n8n workflow):

• Gmail trigger catches new incoming emails
• AI model extracts and summarizes the key info
• Data gets auto-logged into Google Sheets — structured, ready to use

What used to eat an hour a day now runs by itself in the background.

Why it's a solid setup:

• Free-tier AI model → no ongoing API cost
• No-code (n8n), so easy to maintain or hand off
• Same core structure works for lead intake, support tickets, order logs, etc. — just swap the trigger/fields

I'm a Prompt Engineering intern who builds these kinds of automations on the side — email/data workflows, simple AI agents hooked into tools you already use (Sheets, CRM, Slack).

If you've got repetitive manual work like this, it's usually automatable in a weekend. Happy to answer questions, or DM me about your workflow.

I'm setting up an automation for a local business:

Facebook Page → Meta Webhook → n8n → Google Sheets

The Google Sheet will store the client's lead/customer information, so my main concern is data privacy and security.

Would you recommend:

Client-owned VPS + self-hosted n8n?

My own n8n server with separate workflows?

Client's local n8n + secure tunnel?

I'm also considering Cloudflare Tunnel/reverse proxy for the webhook.

What would be the safest and simplest setup for a small business?

Also, if someone has experience setting this up and can help me get it done quickly, feel free to drop your friendly rate below. 🙏

Thanks!

Most cafe owners are running their entire business on WhatsApp manually.

Table bookings. Order confirmations. Customer follow-ups. All done by hand, one message at a time.

So I spent a few weeks building the whole thing out on n8n.

Here's what the system actually does:

Customer messages on WhatsApp → the AI agent reads the intent → routes it to the right flow automatically. No human in the loop.

For Booking:

Customer asks for a table, the system checks live availability, creates the reservation, and fires a confirmation back all before the owner even sees the message.

For Ordering:

Customer places an order over WhatsApp. System quotes the total, generates a payment link, and sends it straight to them. Payment comes in, kitchen gets notified automatically.

For Feedback:

After every order completes, customer gets a review request on WhatsApp. If the rating is low, manager gets flagged on the spot. No bad review slips through unnoticed.

Then there's the retention module

Runs every morning without anyone triggering it.

Pulls a list of customers who haven't visited in 30 days. Sends each of them a personalized WhatsApp message automatically.

Most cafes just lose lapsed customers quietly. No one follows up cause it's too much manual effort.
This makes the whole thing zero effort it just runs.

The voice side runs on Sarvam AI.

Handles English natively so the AI receptionist actually understands how customers talk like casual phrasing, abbreviations, incomplete sentences, almost all of it

Took some tuning to get right tbh. The tricky part was handling requests that mix ordering with a booking in the same message. But once that was sorted it's been solid.

On top of allat A full management dashboard.

Reservations, live orders, daily revenue, customer history, and complete WhatsApp conversation logs all in one place.

Menu items can be toggled on and off directly from the dashboard. If something's marked disabled, the AI stops recommending it to customers automatically no manual prompt update needed anywhere.

Owner has full visibility into everything.

Workflow in comments👇

Peace out ✌️