Capstone: Your Personal Automation Stack

From Individual Workflows to a Stack

The workflows in this track are not isolated tools — they are components of a connected automation system. Lead capture feeds your CRM. Your CRM triggers email sequences. Email sequences generate feedback. Feedback routes to approval workflows. Approvals update your content calendar. When each automation shares data with the others, the total value exceeds the sum of the parts. This lesson is about connecting your automations into a coherent stack.

The Five Archetypes Revisited

Every automation you will ever build fits one of the five archetypes introduced in lesson 1:

• Notification — payment received, lead captured, form submitted, error occurred.
• Sync — contacts updated across CRM and spreadsheet, content published to multiple platforms.
• Generation — email drafts, content briefs turned into articles, weekly digests assembled from data.
• Approval — content sign-off, expense approval, refund authorisation, access requests.
• Report — weekly digest, Slack command reports, NPS summaries.

Map every automation you want to build onto this framework. It will immediately clarify the trigger, the core nodes needed, and the expected outcome.

Your Automation Audit

Spend 15 minutes this week listing every manual, repetitive task you do. For each one, ask:

• Does it happen more than twice a week?
• Does it follow the same steps every time?
• Could the inputs and outputs be described precisely to another person?

Tasks that pass all three tests are automation candidates. Tasks that require genuine judgment or relationship management stay manual — but even those may have automatable steps within them.

Prioritisation: Build the Right Things First

From your audit list, score each candidate on two dimensions:

1. Impact — hours saved per week, plus value of errors prevented (high, medium, low).
2. Effort — how many nodes, integrations, and edge cases are involved (high, medium, low).

Build high-impact, low-effort automations first. These are your quick wins — they deliver immediate value and build your confidence in n8n before you tackle complex workflows. Defer high-effort, low-impact automations indefinitely.

Maintaining What You Build

Running automations break. APIs change, credentials expire, data formats shift. Build maintenance into your process from day one:

• Use n8n's built-in execution logs to review workflow runs weekly for the first month after launch.
• Set up an error workflow for every production automation that posts failures to a dedicated Slack channel.
• Name your workflows, add sticky notes on complex nodes, and keep a short README in a Notion or Google Doc for each automation stack you build.

Your First 30 Days

A practical roadmap:

1. Week 1 — Build one notification automation (payment event, form submission, or API alert).
2. Week 2 — Build one sync automation (CRM contact sync or cross-platform post).
3. Week 3 — Build one report automation (weekly digest or Slack command).
4. Week 4 — Connect two of your automations so output from one feeds into another.

After 30 days you will have a foundation — four working automations, a monitoring setup, and a clear picture of where to expand next.