Capstone Part 1: Architecture & Requirements

Congratulations on reaching the final module. It's time to put everything you've learned into a single, cohesive system. You are building "Nexus-One", an automated back-office for a fictional consulting firm.

1. The Business Requirement

Nexus-One must solve three problems:

1. Lead Intake: New leads from a Webhook must be enriched, scored, and added to a CRM.
2. Support AI: Incoming "Support" emails must be summarized by AI and posted to Slack.
3. Weekly Digest: Every Friday, n8n must gather "Total Sales" from a sheet and email a report to the CEO.

---

2. The Modular Map

We will use the Execute Workflow node (Module 5) to keep things clean.

• Workflow A (The Intake): Webhook -> Enrichment (Module 8) -> HubSpot.
• Workflow B (The Brain): Gmail Trigger -> AI OpenAI (Module 10) -> Slack.
• Workflow C (The Reporter): Schedule Trigger -> Google Sheets (Module 7) -> Gmail.

---

3. Technology Stack

• Engine: n8n (Self-hosted via Docker).
• Intelligence: OpenAI (GPT-4o).
• Storage: Google Sheets & HubSpot.
• Communication: Slack & Gmail.

---

4. Today's Task: The Connection Map

Before you drag a single node, you must set your Credentials:

1. Google OAuth2 (for Sheets/Gmail).
2. HubSpot Private App Token.
3. OpenAI API Key.
4. Slack Webhook URL.

---

Exercise: The Architect's Vision

1. Draw a flowchart showing how data moves between your 3 module workflows.
2. Which node will you use to "Score" the leads in Workflow A? (Review Module 8).
3. If the the AI Summarizer (Workflow B) fails, how will you find out? (Review Module 9).
4. Write down 3 "Custom Fields" you will need in your Google Sheet to track the performance of Nexus-One itself.

---

Summary

Part 1 is about Clarity. By defining the modular structure and the credential requirements of Nexus-One, you ensure that the actual building process in Part 2 is an exercise in "Wiring" rather than "Confusion."

Next Lesson: Part 2: Building the Lead and CRM Engine.