Capture leads on WhatsApp and save them to Sheets
An n8n WhatsApp agent asks leads for their name and email and automatically saves them to Google Sheets, shown in a demo.
An n8n workflow catches customer replies to order confirmations and forwards support requests into Freshdesk.
An n8n workflow catches customer replies to order confirmations and forwards support requests into Freshdesk.
They built an n8n workflow around a dedicated catch-all Gmail inbox for replies to order-confirmation emails. An AI classifier checked each incoming message to decide whether it was a real support request, and if so the workflow forwarded it into Freshdesk instead of sending every reply to support; the post does not describe any manual review step.
It solved the problem of support replies landing in a generic info@ inbox without dumping unrelated mail into the support queue. The author says the first version took about 30 minutes to build, but gives no accuracy or volume numbers.
The main practical catch is that the source stays high level: it names Gmail, an AI classifier, and Freshdesk, but does not share the workflow, prompt, or classification criteria.
Build an n8n workflow that watches [inbox] for customer replies to our order confirmation emails. Classify whether each reply is a support request, and if so create a Freshdesk ticket with the customer's email, order number, and message text. Ignore auto-replies and thank-yous, and finish by testing with two sample replies and showing me the resulting tickets.
An n8n WhatsApp agent asks leads for their name and email and automatically saves them to Google Sheets, shown in a demo.
Score every demo request against your ICP, update HubSpot and ping the right rep in Slack within a minute of the form submit.
Every new Zendesk ticket gets a category, priority and sentiment tag plus a draft reply in an internal note before an agent opens it.