如何构建在你睡觉时管理整个业务的 Claude Agent

✍ CyrilXBT🕐 2026-05-18📦 17.9 KB 🟢 已读 𝕏 文章列表

文章详细介绍了如何构建一个基于 Claude 的全自动业务管理 Agent，用于在用户休息时自动处理邮件、生成报告、追踪项目和客户线索。核心架构由 Claude（智能层）、CLAUDE.md（业务上下文层）、MCP Servers（连接层）和 N8N（自动化层）组成。教程包含了具体的上下文配置模板（CLAUDE.md）、MCP 服务器配置（Gmail, Notion, Calendar 等）以及六个核心自动化工作流的实施步骤，旨在将业务运营从个人依赖转变为系统化智能运行。

Claude AI Agent 自动化业务管理 MCP N8N 工作流 LLM 生产力工具

# How to Build a Claude Agent That Manages Your Entire Business While You Sleep **作者**: CyrilXBT **日期**: 2026-05-18T01:33:23.000Z **来源**: [https://x.com/cyrilXBT/status/2056186353029722587](https://x.com/cyrilXBT/status/2056186353029722587) --- ![Image](/doc/2014/image/img_109bc6db6f5b.jpg) Most business owners spend their days reacting. Emails pile up. Project statuses go stale. Client briefs need compiling. Reports need generating. Content needs drafting. Revenue needs tracking. Follow-ups get missed. Not because they are disorganized. Because they are the operational layer of their own business. Every piece of information that moves from one place to another moves through them. Every status update requires their attention. Every recurring task waits for them to initiate it. The business does not run without them in the loop. This guide is about changing that equation permanently. A Claude agent connected to your tools, configured with your business context, and running automated workflows via N8N does not wait for you to initiate anything. It monitors. It processes. It acts. It reports. While you sleep. ## The Mental Model Shift Before the build, the concept. Most people who try to automate their business build automations. A Zap that sends an email when a form is submitted. A workflow that creates a task when a Slack message is pinged. Individual automations for individual triggers. These are useful. They are not a business management agent. The difference is intelligence and context. An automation executes a fixed sequence when a trigger fires. An agent reads the situation, applies business context, makes a judgment, and takes the appropriate action. When a new lead comes in, an automation sends a templated email. When a new lead comes in, an agent reads the lead's details, checks your CRM for any existing relationship, researches the company, drafts a personalized first message based on their specific situation, schedules it for the optimal send time, and creates a follow-up task for three days later. Same trigger. Completely different output. The agent does what a smart human employee would do. The automation does what a dumb script does. This guide builds the agent. ## The Architecture Four components make a business management agent work. Claude is the intelligence layer. It reads context, makes decisions, generates outputs, and determines what action to take in any given situation. CLAUDE.md is the business context layer. It tells Claude everything about your business before any workflow runs. Your clients. Your standards. Your voice. Your rules. Your current priorities. MCP Servers are the connection layer. They give Claude direct access to your actual business tools. Email. Calendar. CRM. Project management. Database. Communication tools. N8N is the automation layer. It schedules workflows, fires triggers, passes data between systems, and makes the entire operation run without you initiating anything. Together these four components create an agent that manages your business continuously rather than responding to your prompts on demand. ## Building the Business Context Layer The CLAUDE.md file is the foundation everything else rests on. Every workflow the agent runs reads this file first. It is the briefing document that turns generic Claude capability into business-specific intelligence. A poorly written CLAUDE.md produces generic outputs that require significant editing. A precisely written CLAUDE.md produces outputs that could have come from a senior employee who has worked with you for years. # Business Management Agent — CLAUDE.md ## Business Identity Name: [YOUR BUSINESS NAME] What you do: [SPECIFIC ONE-SENTENCE DESCRIPTION] Who you serve: [SPECIFIC CUSTOMER DESCRIPTION] Revenue model: [HOW THE BUSINESS MAKES MONEY] Stage: [EARLY / GROWTH / ESTABLISHED] Monthly revenue: [CURRENT NUMBER — UPDATE MONTHLY] ## Active Clients [CLIENT NAME]: [SERVICE TYPE] | Value: $[MRR] | Status: [CURRENT STATUS] | Next action: [SPECIFIC NEXT STEP] [Repeat for every active client] ## Current Projects [PROJECT NAME]: [DESCRIPTION] | Deadline: [DATE] | Status: [STATUS] | Blocker: [IF ANY] [Repeat for every active project] ## Communication Standards Email tone: [PROFESSIONAL / FRIENDLY / DIRECT] Response time commitment: [YOUR STANDARD] What you never say: [SPECIFIC PHRASES TO AVOID] How you open emails: [YOUR PATTERN] How you close emails: [YOUR PATTERN] ## Decision Authority Agent can act autonomously on: - Scheduling non-urgent internal tasks - Drafting communications for review - Generating reports and summaries - Updating internal records - Routing information between systems Agent must escalate to human before: - Any external communication sent - Any financial transaction - Any client commitment made - Any contract or agreement - Any public-facing content published ## Quality Standards [WHAT GOOD WORK LOOKS LIKE IN YOUR BUSINESS] ## This Week's Focus [UPDATE EVERY MONDAY — current priorities that weight every decision] The Decision Authority section is the most important part of this file. It defines the boundary between what the agent does autonomously and what it flags for human review. Get this wrong in either direction and you either have an agent that does nothing useful or one that makes decisions it should not make. ## The MCP Stack for Business Management The right MCP connections depend on your specific business tools. These are the highest-value connections for most operators. Gmail MCP — Read incoming emails. Categorize by type and urgency. Draft responses. Flag items requiring human review. Monitor for specific triggers like payment notifications or client escalations. Google Calendar MCP — Read your schedule. Create events. Set reminders. Identify scheduling conflicts. Prepare briefings for upcoming calls. Notion or Airtable MCP — Read and update project databases. Update client records. Track task completion. Generate status reports from live data. Stripe MCP — Monitor revenue. Flag payment failures. Track MRR trends. Generate financial summaries. Slack MCP — Post automated updates to channels. Send notifications when workflows complete. Read mentions requiring response. Filesystem MCP — Read and write your local files. Access your Obsidian vault. Save reports and generated content to the right folders. Your claude_desktop_config.json connecting the core stack: { "mcpServers": { "filesystem": { "command": "npx", "args": [ "-y", "@modelcontextprotocol/server-filesystem", "/path/to/your/business/vault" ] }, "gmail": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-gmail"], "env": { "GMAIL_CLIENT_ID": "your-client-id", "GMAIL_CLIENT_SECRET": "your-client-secret" } }, "notion": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-notion"], "env": { "NOTION_API_KEY": "your-key" } }, "gcal": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-google-calendar"], "env": { "GCAL_CLIENT_ID": "your-client-id", "GCAL_CLIENT_SECRET": "your-client-secret" } } } } ## The Six Business Management Workflows These six workflows cover the core functions of running a business. Each one runs automatically via N8N without you initiating anything. Workflow 1: Morning Business Briefing Trigger: Every weekday at 6AM What it does: Read CLAUDE.md for full business context. Compile the morning briefing from these sources: EMAIL: Read all emails received since yesterday 5PM. Categorize each as: CLIENT, PROSPECT, VENDOR, ADMIN, or URGENT. Summarize any requiring response today. CALENDAR: Read today's schedule from Google Calendar. For any external meetings: pull the contact from the CRM, summarize recent communications, prepare 3 agenda items. PROJECTS: Read all project records in Notion. Flag any projects with overdue tasks or approaching deadlines. REVENUE: Check Stripe for any transactions or alerts since yesterday. OUTPUT FORMAT: URGENT (requires action before 10AM): [LIST] TODAY'S SCHEDULE: [WITH PREP NOTES FOR EACH MEETING] EMAIL PRIORITIES: [WHAT NEEDS A RESPONSE TODAY] PROJECT ALERTS: [ANYTHING NEEDING ATTENTION] REVENUE UPDATE: [KEY NUMBERS] ONE FOCUS: [The single most important thing to accomplish today] Save to: /vault/daily-briefings/[DATE]-briefing.md Send summary to Slack #daily-briefing channel. Why it matters: You open your laptop to a complete operational picture. No scrambling through email, calendar, and Slack to understand where you stand. The briefing is waiting. Workflow 2: Email Triage and Draft Generator Trigger: Every 2 hours during business hours What it does: Read all unread emails received in the last 2 hours. For each email: STEP 1: Categorize - CLIENT URGENT: Requires response within 2 hours - CLIENT STANDARD: Requires response within 24 hours - PROSPECT: New potential client inquiry - VENDOR/ADMIN: Does not require urgent response - AUTOMATED: No response needed STEP 2: For CLIENT URGENT and PROSPECT emails: Read the sender's record from the CRM. Read any previous email thread with this sender. Draft a response that: - Addresses every point raised in their email - Matches the communication standards in CLAUDE.md - Includes a specific next step or clear answer - Does NOT commit to anything in the Decision Authority escalation list STEP 3: Save drafts to /vault/email-drafts/[DATE]-drafts.md STEP 4: Send Slack notification listing emails requiring review with draft locations Do not send any email. Prepare drafts for human review only. Why it matters: Email triage that used to take 45 minutes happens automatically. You arrive at your review queue with drafts already written. You approve or edit. You send. The back-and-forth of writing from scratch is eliminated. Workflow 3: Client Relationship Monitor Trigger: Every Monday at 7AM What it does: Read all active client records from CLAUDE.md and the CRM. For each client: COMMUNICATION HEALTH CHECK: - When was the last communication? - Is there any open item without a response? - Is any deliverable overdue? RELATIONSHIP SCORE: Rate the relationship health as: HEALTHY, ATTENTION NEEDED, or AT RISK Based on: recency of contact, open issues, delivery status ACTION REQUIRED: For ATTENTION NEEDED: Draft a check-in message For AT RISK: Flag as urgent and summarize the situation UPSELL OPPORTUNITY: Based on the client's usage and stated goals, identify if there is a natural expansion opportunity worth raising Save weekly CRM report to: /vault/crm-reports/[DATE]-crm.md Send Slack alert for any AT RISK clients immediately. Why it matters: Client churn is expensive. The relationship monitor catches problems before they become cancellations. An at-risk client flagged Monday morning can be saved with a well-timed conversation. The same client flagged after they have already decided to leave cannot. Workflow 4: Revenue and Financial Tracking Trigger: First day of every month at 8AM What it does: Read all Stripe transactions from the previous month. Read expense records from the business folder. Read revenue target from CLAUDE.md. Generate monthly financial report: REVENUE SUMMARY: - Total MRR - New MRR (new clients started) - Expansion MRR (upsells) - Churned MRR (cancellations) - Net new MRR - Total vs target (percentage) CLIENT BREAKDOWN: - Revenue by client - Clients at risk of churning based on engagement signals EXPENSE SUMMARY: - Total expenses by category - Month over month comparison - Largest expense categories PROJECTION: - Current run rate - Projected quarterly total - Gap to annual target RECOMMENDATIONS: - One action to increase revenue this month - One cost reduction opportunity if any exists Save to: /vault/finances/[YEAR]-[MONTH]-financial-report.md Update the revenue figure in CLAUDE.md. Why it matters: Financial clarity without a manual process. You start every month knowing exactly where you stand without spending an hour pulling numbers from Stripe and spreadsheets. Workflow 5: Project Status Auto-Updater Trigger: Continuous — fires when you log completions in your daily note What it does: When you write DONE: [project] — [task] in your daily note: Read the completion entry from today's daily note. Find the corresponding project record in Notion. Mark the specified task as complete with today's timestamp. Check if this completion triggers any dependent tasks. If yes: update dependent task status to READY. Check if all tasks in the current phase are complete. If yes: advance the project to the next phase. Update the project overview with current completion percentage. Send Slack notification: "[Project] — [Task] completed. Project is now [X]% complete." Why it matters: Project management that updates itself. You log what you did once. The project database reflects reality automatically. The stakeholder notification goes out automatically. You never manually update a project status again. Workflow 6: Weekly Business Review Trigger: Every Sunday at 7PM What it does: Read all daily notes from the past 7 days. Read all project status changes this week. Read the email triage logs from this week. Read the financial transactions from this week. Read the client relationship report from Monday. Generate the weekly business review: WHAT MOVED FORWARD: Specific projects, clients, and metrics that improved The cause of each improvement WHAT DID NOT MOVE: Honest assessment of what stalled The most likely reason for each THE PATTERN THIS WEEK: One theme that appeared repeatedly across the week Whether it is positive or needs addressing NEXT WEEK'S PRIORITIES: Three specific priorities ranked by business impact For each: why it matters and the specific next action ONE DECISION TO MAKE: The most important decision sitting on the table The information you have to make it What happens if you delay it one more week Save to: /vault/weekly-reviews/[DATE]-review.md Why it matters: The weekly review is the highest-leverage hour in any business. Done well it surfaces patterns that daily operations obscure and identifies the decisions that compound. Done automatically it requires 15 minutes of reading instead of 90 minutes of manual compilation. ## Setting Up the N8N Orchestration Layer All six workflows run via N8N. Self-hosted on a $5 DigitalOcean droplet. Each workflow follows the same N8N structure: Trigger Node → Read CLAUDE.md → Prepare context prompt → Claude API call → Process output → Write to vault → Send notification → Log operation The Claude API call always passes the CLAUDE.md contents as system context. This is what makes every automated output business-specific rather than generic. For the email triage workflow the structure has an additional branch: Gmail webhook → Filter non-automated emails → Read sender CRM record → Prepare draft context → Claude API call → Save draft → Slack notification The Gmail webhook requires a configured Gmail API connection in N8N. This is the most technically involved setup step and typically takes 30 to 45 minutes the first time. ## The First 30 Days The agent does not run perfectly from day one. The first week surfaces gaps in your CLAUDE.md. The email triage uses language that does not match your voice. The morning briefing prioritizes the wrong things. The project updater misses a workflow. Each gap is a two-minute CLAUDE.md edit. By day 14 the outputs require less editing than they did in week one. By day 30 the morning briefing is accurate enough that you make decisions from it without checking the sources. The email drafts sound like you wrote them on your best day. The weekly review captures things you would have missed in a manual review. The compounding starts at day one. It becomes visible at day 30. It becomes indispensable at day 90. ## What Changes When It Works The shift that happens when a business management agent is running correctly is not that you work less. It is that the work you do is different. Before the agent: You start every day reacting to email, manually updating project statuses, compiling information that already exists in your tools, and handling the administrative coordination that keeps everything from falling behind. After the agent: You start every day reading a briefing that is already compiled, reviewing drafts that are already written, seeing project statuses that are already updated, and making decisions about things that actually require your judgment. The administrative coordination layer of your business runs itself. What remains is the work only you can do. Strategy. Relationships. Creative decisions. The judgment calls that make the difference between a good business and a great one. That is what the agent frees you to focus on. Build it this weekend. Start with the morning briefing workflow. Add one workflow per week. By month two your business manages itself while you sleep. Follow @cyrilXBT for the exact N8N workflows, CLAUDE.md templates, and MCP configurations that power this entire system. ## 相关链接 - [CyrilXBT](https://x.com/cyrilXBT) - [@cyrilXBT](https://x.com/cyrilXBT) - [6.8K](https://x.com/cyrilXBT/status/2056186353029722587/analytics) - [@modelcontextprotocol/server-filesystem](https://x.com/@modelcontextprotocol/server-filesystem) - [@modelcontextprotocol/server-gmail](https://x.com/@modelcontextprotocol/server-gmail) - [@modelcontextprotocol/server-notion](https://x.com/@modelcontextprotocol/server-notion) - [@modelcontextprotocol/server-google-calendar](https://x.com/@modelcontextprotocol/server-google-calendar) - [#daily](https://x.com/search?q=%23daily&src=hashtag_click) - [@cyrilXBT](https://x.com/@cyrilXBT) - [Upgrade to Premium](https://x.com/i/premium_sign_up) - [9:33 AM · May 18, 2026](https://x.com/cyrilXBT/status/2056186353029722587) - [6,831 Views](https://x.com/cyrilXBT/status/2056186353029722587/analytics) - [View quotes](https://x.com/cyrilXBT/status/2056186353029722587/quotes) --- *导出时间: 2026/5/18 14:21:52* --- ## 中文翻译 # 如何构建一个 Claude Agent，在你睡觉时管理你的整个业务 **作者**: CyrilXBT **日期**: 2026-05-18T01:33:23.000Z **来源**: [https://x.com/cyrilXBT/status/2056186353029722587](https://x.com/cyrilXBT/status/2056186353029722587) --- ![Image](/doc/2014/image/img_109bc6db6f5b.jpg) 大多数企业主都在终日应付。邮件堆积如山。项目状态停滞不前。客户简报需要整理。报告需要生成。内容需要起草。收入需要追踪。后续跟进被遗忘。并不是因为他们缺乏条理。而是因为他们自身就是业务运营层。每一条从一个地方流转到另一个地方的信息都必须经过他们。每一次状态更新都需要他们关注。每一项重复性任务都在等待他们去启动。没有他们的参与，业务就无法运转。本指南旨在永久改变这一等式。一个连接了你的工具、配置了你的业务背景并通过 N8N 运行自动化工作流的 Claude Agent，不需要等待你去启动任何操作。它监控。它处理。它行动。它汇报。当你沉睡时。 ## 思维模式的转变在构建之前，先理解概念。大多数试图实现业务自动化的人构建的是“自动化”。当表单提交时发送邮件的 Zap。当 Slack 消息被 ping 时创建任务的工作流。针对单个触点的独立自动化。这些很有用。但它们不是业务管理代理。区别在于智能和上下文。自动化在触发器被触发时执行固定的序列。代理则读取情况，应用业务背景，做出判断，并采取适当的行动。当新线索进来时，自动化会发送一封模板邮件。当新线索进来时，代理会阅读线索的详细信息，检查你的 CRM 是否存在任何既有关系，调研该公司，根据他们的具体情况起草个性化的首条消息，安排在最佳发送时间发送，并创建一个三天后的跟进任务。同样的触发。完全不同的输出。代理所做的就像一位聪明的人类员工会做的事。自动化所做的就像一段愚蠢的脚本。本指南将构建这个代理。 ## 架构四个组件让业务管理代理发挥作用。 Claude 是智能层。它读取上下文，做出决策，生成输出，并确定在给定情况下采取什么行动。 CLAUDE.md 是业务上下文层。它告诉 Claude 关于你业务的一切，在任何工作流运行之前。你的客户。你的标准。你的语调。你的规则。你当前的重心。 MCP 服务器是连接层。它们赋予 Claude 对你实际业务工具的直接访问权限。邮件。日历。CRM。项目管理。数据库。沟通工具。 N8N 是自动化层。它调度工作流，触发触发器，在系统之间传递数据，并让整个操作在无需你启动任何东西的情况下运行。这四个组件共同创建了一个持续管理你业务的代理，而不是按需响应你的提示。 ## 构建业务上下文层 CLAUDE.md 文件是所有其他部分的基础。代理运行的每个工作流都会首先读取这个文件。它是将通用 Claude 能力转化为特定业务智能的简报文档。写得糟糕的 CLAUDE.md 会产生通用输出，需要大量编辑。写得精确的 CLAUDE.md 会产生那种可能来自和你共事多年的资深员工的输出。 # 业务管理代理 — CLAUDE.md ## 业务身份名称：[你的业务名称] 业务内容：[具体的一句话描述] 服务对象：[具体客户描述] 收入模式：[业务如何赚钱] 阶段：[早期 / 成长期 / 成熟期] 月收入：[当前数字 — 每月更新] ## 活跃客户 [客户名称]：[服务类型] | 价值：$[MRR] | 状态：[当前状态] | 下一步行动：[具体下一步骤] [为每个活跃客户重复此条目] ## 当前项目 [项目名称]：[描述] | 截止日期：[日期] | 状态：[状态] | 阻碍因素：[如有] [为每个活跃项目重复此条目] ## 沟通标准邮件语调：[专业 / 友好 / 直接] 响应时间承诺：[你的标准] 禁忌语：[需避免的具体短语] 邮件开头方式：[你的模式] 邮件结尾方式：[你的模式] ## 决策权限代理可自主执行： - 安排非紧急内部任务 - 起草待审沟通内容 - 生成报告和摘要 - 更新内部记录 - 在系统之间路由信息代理必须在以下情况升级给人类： - 发送任何外部沟通 - 进行任何财务交易 - 做出任何客户承诺 - 签署任何合同或协议 - 发布任何面向公众的内容 ## 质量标准 [在你的业务中，什么是好的工作表现] ## 本周重点 [每周一更新 — 影响每个决策的当前优先事项] “决策权限”部分是本文件中最重要的部分。它定义了代理自主做什么与标记给人类审核之间的界限。如果这一步在任何一个方向上出错，你要么会得到一个没有任何用处的代理，要么会得到一个做出不当决策的代理。 ## 用于业务管理的 MCP 技术栈正确的 MCP 连接取决于你的具体业务工具。以下是对于大多数运营者来说价值最高的连接。 Gmail MCP — 阅读收到的邮件。按类型和紧急程度分类。起草回复。标记需要人工审核的项目。监控特定触发器，如付款通知或客户升级。 Google Calendar MCP — 阅读你的日程。创建事件。设置提醒。识别日程冲突。为即将到来的电话准备简报。 Notion 或 Airtable MCP — 阅读和更新项目数据库。更新客户记录。追踪任务完成情况。根据实时数据生成状态报告。 Stripe MCP — 监控收入。标记付款失败。追踪 MRR 趋势。生成财务摘要。 Slack MCP — 在频道中发布自动更新。当工作流完成时发送通知。阅读需要回复的提及。 Filesystem MCP — 读写你的本地文件。访问你的 Obsidian 知识库。将报告和生成的内容保存到正确的文件夹。连接核心技术栈的 `claude_desktop_config.json`： ```json { "mcpServers": { "filesystem": { "command": "npx", "args": [ "-y", "@modelcontextprotocol/server-filesystem", "/path/to/your/business/vault" ] }, "gmail": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-gmail"], "env": { "GMAIL_CLIENT_ID": "your-client-id", "GMAIL_CLIENT_SECRET": "your-client-secret" } }, "notion": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-notion"], "env": { "NOTION_API_KEY": "your-key" } }, "gcal": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-google-calendar"], "env": { "GCAL_CLIENT_ID": "your-client-id", "GCAL_CLIENT_SECRET": "your-client-secret" } } } } ``` ## 六大业务管理工作流这六个工作流涵盖了经营业务的核心功能。每一个都通过 N8N 自动运行，无需你启动任何操作。 **工作流 1：早晨业务简报** **触发器**：每个工作日上午 6 点 **作用**：阅读 CLAUDE.md 以获取完整业务上下文。从以下来源汇编晨间简报： **邮件**：阅读自昨天下午 5 点以来收到的所有邮件。将每封邮件分类为：客户、潜在客户、供应商、行政或紧急。总结今天需要回复的邮件。 **日历**：从 Google Calendar 阅读今天的日程。对于任何外部会议：从 CRM 中提取联系人，总结最近的沟通，准备 3 个议程项。 **项目**：阅读 Notion 中的所有项目记录。标记有过期任务或临近截止日期的项目。 **收入**：检查 Stripe 自昨天以来的任何交易或警报。 **输出格式：** 紧急（上午 10 点前需要行动）：[列表] 今日日程：[每次会议的准备笔记] 邮件优先级：[今天需要回复的内容] 项目警报：[任何需要注意的事项] 收入更新：[关键数字] 单一焦点：[今天要完成的唯一最重要事项] 保存至：`/vault/daily-briefings/[DATE]-briefing.md` 发送摘要到 Slack #daily-briefing 频道。 **重要性**：你打开笔记本电脑就能看到完整的运营图景。无需在邮件、日历和 Slack 之间翻找来了解你的处境。简报正等着你。 **工作流 2：邮件分类和草稿生成器** **触发器**：工作时间内每 2 小时 **作用**：阅读过去 2 小时内收到的所有未读邮件。对于每封邮件： **步骤 1：分类** - 客户紧急：需要在 2 小时内回复 - 客户标准：需要在 24 小时内回复 - 潜在客户：新潜在客户咨询 - 供应商/行政：无需紧急回复 - 自动化：无需回复 **步骤 2：对于“客户紧急”和“潜在客户”邮件：** 从 CRM 读取发件人记录。阅读与该发件人的既往邮件线程。起草回复，要求： - 回复他们邮件中提出的每一点 - 符合 CLAUDE.md 中的沟通标准 - 包含具体的下一步骤或明确答案 - **不**承诺决策权限升级列表中的任何事项 **步骤 3：** 将草稿保存至 `/vault/email-drafts/[DATE]-drafts.md` **步骤 4：** 发送 Slack 通知，列出需要审核的邮件及草稿位置不要发送任何邮件。仅准备草稿供人工审核。 **重要性**：过去需要 45 分钟的邮件分类现在自动完成。当你到达审核队列时，草稿已经写好。你批准或编辑。发送。从零开始反复撰写的过程被消除了。 **工作流 3：客户关系监控** **触发器**：每周一上午 7 点 **作用**：从 CLAUDE.md 和 CRM 中读取所有活跃客户记录。对于每个客户： **沟通健康检查：** - 上次沟通是什么时候？ - 是否有任何未回复的待办事项？ - 是否有任何交付成果逾期？ **关系评分：** 将关系健康状况评为：健康、需要注意或有风险基于：联系最近度、未解决问题、交付状态 **所需行动：** 对于“需要注意”：起草一条问候消息对于“有风险”：标记为紧急并总结情况 **追加销售机会：** 根据客户的使用情况和既定目标，识别是否存在值得提出的自然扩展机会将每周 CRM 报告保存至：`/vault/crm-reports/[DATE]-crm.md` 立即发送 Slack 警报通知任何“有风险”的客户。 **重要性**：客户流失代价高昂。关系监控在问题变成取消之前捕捉到它们。周一早上被标记的有风险客户可以通过一次及时对话来挽救。而在客户已经决定离开之后才被标记的同一客户则无法挽回。 **工作流 4：收入和财务追踪** **触发器**：每月第一天上午 8 点 **作用**：读取上个月的所有 Stripe 交易。从业务文件夹读取支出记录。从 CLAUDE.md 读取收入目标。生成月度财务报告： **收入摘要：** - 总月度经常性收入 (MRR) - 新增 MRR（新客户启动） - 扩展 MRR（追加销售） - 流失 MRR（取消） - 净增 MRR - 总额与目标对比（百分比） **客户细分：** - 按客户统计收入 - 基于参与信号有流失风险的客户 **支出摘要：** - 按类别统计的支出总额 - 环比比较 - 最大的支出类别 **预测：** - 当前运营速率 - 预计季度总额 - 距离年度目标的差距 **建议：** - 本月增加收入的一项行动 - 如果存在，一项降低成本的机会保存至：`/vault/finances/[YEAR]-[MONTH]-financial-report.md` 更新 CLAUDE.md 中的收入数字。 **重要性**：无需人工流程即可获得财务清晰度。每个月开始时，你都确切知道自己的处境，无需花一小时从 Stripe 和电子表格中提取数字。 **工作流 5：项目状态自动更新器** **触发器**：连续 — 当你在每日笔记中记录完成情况时触发 **作用**：当你在每日笔记中写下 `DONE: [project] — [task]` 时：从今天的每日笔记中读取完成条目。在 Notion 中找到相应的项目记录。将指定任务标记为完成，并带有今天的时间戳。检查此完成是否触发任何依赖任务。如果是：将依赖任务状态更新为准备就绪。检查当前阶段的所有任务是否完成。如果是：将项目推进到下一阶段。用当前完成百分比更新项目概览。发送 Slack 通知：“[项目] — [任务] 已完成。项目现在已完成 [X]%。” **重要性**：自我更新的项目管理。你只需记录一次你所做的工作。项目数据库自动反映现实。利益相关者通知自动发出。你再也不会手动更新项目状态。 **工作流 6：每周业务复盘** **触发器**：每周日晚 7 点 **作用**：阅读过去 7 天的所有每日笔记。阅读本周的所有项目状态变更。阅读本周的邮件分类日志。阅读本周的财务交易。阅读周一的客户关系报告。生成每周业务复盘： **取得了哪些进展：** 具体得到改善的项目、客户和指标每个改善的原因 **哪些没有进展：** 对停滞内容的诚实评估每个停滞最可能的原因 **本周的模式：** 本周反复出现的一个主题它是积极的还是需要解决 **下周的优先事项：** 按业务影响排名的三个具体优先事项对于每一项：为什么重要以及具体的下一步行动 **需要做出的一项决定：** 摆在桌面上最重要的决定你拥有的用于做决定的信息如果再拖延一周会发生什么保存至：`/vault/weekly-reviews/[DATE]-review.md` **重要性**：每周复盘是任何业务中杠杆率最高的一小时。做得好，它能揭示日常运营所掩盖的模式，并识别出具有复利效应的决策。如果自动完成，它只需要 15 分钟的阅读，而不是 90 分钟的人工汇编。 ## 设置 N8N 编排层所有六个工作流都通过 N8N 运行。自托管在 5 美元的 DigitalOcean Droplet 上。每个工作流遵循相同的 N8N 结构：触发节点 → 读取 CLAUDE.md → 准备上下文提示 → Claude API 调用 → 处理输出 → 写入知识库 → 发送通知 → 记录操作 Claude API 调用始终将 CLAUDE.md 内容作为系统上下文传递。这就是让每个自动化输出都具有业务针对性而不是通用的原因。对于邮件分类工作流，该结构有一个额外的分支： Gmail webhook → 过滤非自动化邮件 → 阅读发件人 CRM 记录 → 准备草稿上下文 → Claude API 调用 → 保存草稿 → Slack 通知 Gmail webhook 需要在 N8N 中配置 Gmail API 连接。这是技术上最复杂的设置步骤，通常第一次需要 30 到 45 分钟。 ## 前 30 天代理并不会在第一天就完美运行。第一周会暴露出你的 CLAUDE.md 中的漏洞。邮件分类使用了与你的语调不符的语言。早晨简报优先考虑了错误的事情。项目更新器遗漏了某个工作流。每个漏洞都是一次两分钟的 CLAUDE.md 编辑。到第 14 天，输出所需的编辑比第一周要少。到第 30 天，早晨简报已经足够准确，你可以直接根据它做出决策而无需查证来源。邮件草稿听起来就像你在状态最好时写的一样。每周复盘捕捉到了你在人工复盘时会遗漏的事情。复利从第一天就开始了。它在……时变得显而易见

🔗 相关文档