8个真实n8n自动化案例：发票处理与线索富化实战

8 个真实的 n8n 自动化案例（含用例与成效）

网上大多数 n8n 示例都很简单：把 Gmail 和 Slack 连起来，当表格新增一行时通知频道。用来学习工具够用，但无法了解它在真实业务中能做什么。以下是我们为客户实际构建和部署的 8 个自动化流程。

1. Invoice reconciliation pipeline

发票对账流程

What it does: ingests PDF invoices from email attachments, extracts structured data with Claude Vision, matches each invoice against open POs in a PostgreSQL database, auto-approves matches above 98% confidence, and sends a Telegram alert for exceptions with the discrepancy highlighted.

功能：从邮件附件中提取 PDF 发票，用 Claude Vision 提取结构化数据，在 PostgreSQL 数据库中匹配每张发票与未结采购订单，置信度超过 98% 的匹配自动审批，异常情况发送 Telegram 告警并高亮显示差异。

Trigger: email received with PDF attachment

触发器：收到带 PDF 附件的邮件

Tools connected: Gmail, Claude API, PostgreSQL, Telegram

接入工具：Gmail、Claude API、PostgreSQL、Telegram

Outcome: 97%+ invoices processed without human involvement, monthly close time cut from 5 days to 1

成效：97%+ 发票无需人工介入即可处理，月结时间从 5 天缩短至 1 天

2. Lead enrichment and qualification

线索丰富与资质审核

What it does: when a form is submitted, the workflow fetches company data from Apollo, passes the enriched record to Claude to score ICP fit (1-5) with reasoning, routes high-scoring leads to a specific rep in the CRM with a Slack notification, and drops low-scoring leads into an automated nurture sequence.

功能：表单提交后，工作流从 Apollo 获取公司数据，将丰富后的记录传给 Claude 打 ICP 契合度分数（1-5）并附带推理依据，高分线索路由至 CRM 中对应的销售并发送 Slack 通知，低分线索进入自动培育流程。

Trigger: webhook from website form

触发器：网站表单 webhook

Tools connected: Apollo, Claude API, HubSpot, Slack

接入工具：Apollo、Claude API、HubSpot、Slack

Outcome: rep research time cut from 2+ hours/day to 20 minutes

成效：销售每天研究时间从 2 小时以上缩短至 20 分钟

3. Production reporting bot

生产报表机器人

What it does: field operators submit production numbers via Telegram throughout the day. n8n aggregates all inputs, calculates totals and variances against targets, Claude formats a plain-English daily summary, and leadership receives the report in Telegram each evening without anyone compiling it manually.

功能：现场操作员全天通过 Telegram 提交生产数据。n8n 汇总所有输入，计算合计数及与目标的偏差，Claude 将每日摘要整理成简明英文，领导每天晚间在 Telegram 收到报表，无需任何人手动汇总。

Trigger: scheduled (6pm daily) + Telegram message listener

触发器：定时触发（每天下午 6 点）+ Telegram 消息监听器

Tools connected: Telegram Bot API, PostgreSQL, Claude API

接入工具：Telegram Bot API、PostgreSQL、Claude API

Outcome: daily reporting shift from 45 minutes of manual aggregation to zero

成效：每日报表从手动汇总 45 分钟变为零人力

4. WhatsApp customer support

WhatsApp 客户支持

What it does: incoming WhatsApp messages are classified by Claude into categories (order status, returns, product question, complaint, other). FAQ-type queries are answered directly from a knowledge base. Complaints and complex queries are routed to a human with a summary. All interactions are logged to the CRM with classification and resolution status.

功能：收到的 WhatsApp 消息由 Claude 分类（订单状态、退货、产品问题、投诉、其他）。常见问题直接从知识库回复。投诉和复杂问题路由给人工并附带摘要。所有对话记录到 CRM，包含分类和解决状态。

Trigger: incoming WhatsApp message via Business API webhook

触发器：通过 Business API webhook 接收 WhatsApp 消息

Tools connected: WhatsApp Business API, Claude API, HubSpot

接入工具：WhatsApp Business API、Claude API、HubSpot

Outcome: 75% of queries handled without human, response time under 2 minutes 24/7

成效：75% 的咨询无需人工处理，响应时间全天候保持在 2 分钟以内

5. Competitor monitoring

竞品监控

What it does: every Monday at 7am, n8n scrapes the pricing pages and feature pages of 5 competitor sites. Claude compares the current content to the version from last week and writes a brief highlighting what changed - new pricing, removed features, new product announcements. The brief lands in Slack before the team starts their week.

功能：每周一早上 7 点，n8n 抓取 5 个竞品的定价页和功能页。Claude 将当前内容与上周版本对比，撰写简报高亮变化——新定价、移除的功能、新产品发布。简报在团队开始新一周工作前到达 Slack。

Trigger: weekly cron (Monday 7am)

触发器：每周定时（周一早 7 点）

Tools connected: HTTP scraper, PostgreSQL (stores previous versions), Claude API, Slack

接入工具：HTTP 抓取工具、PostgreSQL（存储历史版本）、Claude API、Slack

Outcome: competitive changes caught immediately instead of weeks later

成效：竞品变化立即捕获，而非延迟数周才发现

6. Contract expiry monitoring

合同到期监控

What it does: a daily job queries a PostgreSQL contracts table for contracts expiring in the next 30, 60, and 90 days. For each one, Claude drafts a personalized renewal outreach email using the contract details. Drafts go into a review queue in Notion. The sales rep reads and approves or edits, then sends. No contract slips through unrenewed.

功能：每日任务查询 PostgreSQL 合同表中未来 30、60、90 天内到期的合同。针对每份合同，Claude 根据合同详情起草个性化的续约联络邮件。草稿进入 Notion 审核队列。销售阅读后审批或修改，然后发送。不遗漏任何未续约的合同。

Trigger: scheduled daily

触发器：每日定时触发

Tools connected: PostgreSQL, Claude API, Notion

接入工具：PostgreSQL、Claude API、Notion

Outcome: contract renewal rate increased, manual tracking spreadsheet eliminated

成效：合同续约率提升，手动追踪表格取消

7. E-commerce abandoned cart recovery

电商购物车挽回

What it does: when a Shopify checkout is abandoned, n8n waits 2 hours, then passes the cart details (products, prices, customer history) to Claude. Claude writes a personalized recovery email referencing what was left in the cart. The email is sent via Klaviyo from the brand's sending domain. Not a template - a generated email specific to that cart.

功能：当 Shopify checkout 被放弃时，n8n 等待 2 小时，然后将购物车详情（产品、价格、客户历史）传给 Claude。Claude 撰写个性化挽回邮件，提及留在购物车里的商品。邮件通过 Klaviyo 从品牌发件域名发送。不是模板——而是为该购物车专门生成的邮件。

Trigger: Shopify webhook (checkout abandoned)

触发器：Shopify webhook（checkout 放弃）

Tools connected: Shopify, Claude API, Klaviyo

接入工具：Shopify、Claude API、Klaviyo

Outcome: recovery rate 2x compared to previous template-based sequence

成效：挽回率是之前模板序列的 2 倍

8. Supplier reorder automation

供应商补货自动化

What it does: a daily job checks inventory levels for each SKU in a Google Sheet. When a SKU drops below the reorder threshold, Claude drafts a purchase order email to the supplier including SKU, quantity needed, and delivery address. The draft goes to a Telegram approval queue. One tap to send. All orders are logged to a tracking sheet.

功能：每日任务检查 Google Sheet 中每个 SKU 的库存水平。当某个 SKU 低于补货阈值时，Claude 起草采购订单邮件给供应商，包含 SKU、需补数量和收货地址。草稿进入 Telegram 审批队列，一键发送。所有订单记录到追踪表。

Trigger: scheduled daily

触发器：每日定时触发

Tools connected: Google Sheets, Claude API, Gmail, Telegram

接入工具：Google Sheets、Claude API、Gmail、Telegram

Outcome: stockouts eliminated, reorder process cut from 1 hour to 5 minutes per week

成效：缺货问题消除，补货流程从每周 1 小时缩短至 5 分钟

Getting started with n8n

开始使用 n8n

Verified September 2026 on n8n's own pricing page: cloud Starter is 20 EUR/month for 2,500 workflow executions, Pro is 50 EUR for 10,000, Business is 667 EUR for 40,000. Note the unit - n8n bills per workflow execution regardless of how many steps are inside it, which is why deep workflows are far cheaper here than on platforms that bill per module. Self-hosted community edition costs nothing to licence and runs on a VPS for $5-50/month with no execution limit, in exchange for owning uptime, updates and backups yourself.

截至 2026 年 9 月在 n8n 官方定价页验证：云端 Starter 20 欧元/月含 2,500 次工作流执行，Pro 50 欧元含 10,000 次，Business 667 欧元含 40,000 次。注意计费单位——n8n 按工作流执行次数计费，不论内部有多少步骤，这就是为什么深度工作流在这里比按模块计费的平台便宜得多。自托管社区版免费授权，运行在 5-50 美元/月的 VPS 上且无执行次数限制，代价是自己负责可用性、更新和备份。

What these cost to build

这些项目的构建成本

Rough bands for the eight above, so the list is useful rather than aspirational. A scheduled report or a reorder flow like numbers 3 and 8 is one to three days and $1,200-2,500. A qualification or support flow with a model doing judgment, numbers 2 and 4, is $2,500-6,000. The document pipeline in number 1 is $4,000-8,000, mostly because of the matching logic and the ERP integration rather than the extraction.

以上 8 个项目的大致成本区间，力求实用而非空谈。定时报表或补货流程（第 3 和第 8 个）需 1-3 天，费用 $1,200-2,500。需要模型做判断的资质审核或支持流程（第 2 和第 4 个）费用 $2,500-6,000。第 1 个的文档管道 $4,000-8,000，主要成本在匹配逻辑和 ERP 集成而非数据提取。

The part these examples hide

这些示例隐藏的部分

Each description above is the happy path, and the happy path is roughly a fifth of the work. What separates a demo from something you can leave running is the unglamorous half: what happens when a third-party API returns an error halfway through, whether a retried webhook can process the same record twice, whether a failure is loud or silent, and who finds out.

以上每个描述都是 Happy Path，而 Happy Path 大约只占工作的五分之一。区分演示与可放手运行的东西的，是那些不光鲜的另一半：第三方 API 执行到一半返回错误怎么办，重试的 webhook 能否重复处理同一条记录，失败是响亮还是静默的，以及谁来发现。

That is also where the price difference between quotes comes from. If two builders quote the same flow and one is half the price, the difference is almost always error handling, and you will meet it later.

报价差异也来自这里。如果两个 builders 报同一个流程，一个价格是的一半，差异几乎总是在错误处理上，而你会 later 在生产中遇到它。

The learning curve is real: plan a day or two with the interface before building anything production. Start with a flow where a silent failure would be merely annoying rather than expensive, and add the error handling from the first build rather than after the first incident.

学习曲线是真实存在的：正式构建生产环境前，花一两天熟悉界面。从一个静默失败只是让人烦恼而非代价高昂的流程开始，并在第一次构建时就加入错误处理，而非等到第一次事故之后。

Want one of these automations built for your business? Book a free audit call and we'll scope exactly what it takes.

想为你的业务构建其中一个自动化流程？预约免费审计电话，我们来精确评估需要什么。

Originally published at 2pizza.team. We build AI and automation systems for small teams - fixed price, two to six weeks. See the work.

原文发表于 2pizza.team。我们为小团队构建 AI 和自动化系统——固定价格，两到六周交付。看我们的作品。

For further actions, you may consider blocking this person and/or reporting abuse