Build a website-derived support knowledge base with Firecrawl and Gemini, then use it to answer Gmail inquiries in n8n
An n8n tutorial maps and scrapes a business website, has Gemini organise the content into a Google Doc, and connects that knowledge base to a Gmail agent. The example is a lawn-care business, with reusable support mechanics.
Evidence: The source shows its work: steps, screenshots, code or data you can inspect.
The business problem
Customer answers are scattered across website pages, making repeated email questions difficult to handle consistently.
What was tried
Use Firecrawl to map website URLs and batch-scrape Markdown. Ask Gemini 2.5 to organise facts, cite page IDs, flag contradictions and mark missing details unknown. Save the result as a Google Doc through Google Drive. A Gmail-triggered agent retrieves that document, decides whether it can answer, sends eligible replies and logs decisions. The shared prompt tells it to skip personal messages, unsupported questions and knowledge-base loading failures.
What was reported (not reported)
The author provides prompts, a walkthrough and workflow JSON. Support accuracy, customer outcomes and time savings are not measured in the post.
Limitations
The demonstrated business is offline lawn care; online-business use requires adapting its categories and policies. Replies are sent automatically. Prompt instructions are not evidence that invented answers or missed inquiries are prevented.
What you need
n8n, Firecrawl, Gemini, Gmail, Google Docs/Drive and a business website to use as source material.
Sources
- u/dudeson55 on r/n8n ↗ Community discussion, publication date unknown, main source
- lucaswalter: linked n8n Gmail agent JSON ↗ Code repository, publication date unknown
Source published: unknown. Last reviewed here: October 15, 2026. Spot a mistake? Tell us.
Tools in this workflow
- Firecrawl: Maps and scrapes the websiteTry Firecrawl
- n8n: Runs knowledge-base building and email handlingTry n8n
- Gmail: Receives inquiries and sends answersTry Gmail
- Gemini: Organises website facts and reasons over inquiriesTry Gemini
- Google Docs: Stores the support knowledge baseTry Google Docs
Related workflows
Pick an AI model and post-editing setup per content type for Chinese localization, using a blind 774-output benchmark
A localization benchmark found AI workflows beat human translators on four of six content types, but humans led on informational and SEO text, and model choice mattered more than post-editing.
Run AI VPs of marketing and customer success on Replit for about $254 a month, with 3 to 5 hours of weekly upkeep
SaaStr describes two in-house AI agents that run a Monday marketing standup and manage 100+ conference sponsors, with the invoice costs and the human maintenance time it admits they still need.
Keep customer lookup ahead of payment links in an n8n sales agent: a reported two-sale failure and a tool-sequencing fix
A builder reports that a WhatsApp sales agent skipped customer lookup and sent broken Stripe links. They describe a community node that exposes tools one at a time, while commenters question whether the payment path needs an agent.
Save AI-written customer replies in Gmail Drafts, flag missing facts and notify Slack before a person sends
An n8n builder shares a Gmail reply workflow that filters automated senders and leaves sending to a person. The linked JSON adds business context, missing-fact placeholders, draft checks and Slack notifications.