What’s up everyone! First wanted to say thank you for being here. I really do want this community to be a hub to get real time help on workflows, feedback on proposals and SOW, and tips and tricks on how to run an AI agency. I know when I was starting out, this was something I wish I had. You might have noticed that this community is now a paid community. For those joining in the future, it will be $39/mo or $369/yr. What does this mean for you? It means the people joining will be serious about n8n, cursor, and building/scaling an AI automation agency. The dream is increased engagement, potent weekly calls, and everyone increasing their automation capabilities and business acumen. This also means that the 3 events we have on the calendar are now open for anyone to join! The 3 events are: - Help build your workflows: a fist come first serve we break down your workflow you have and see how to fix or improve it - Let’s talk business: here is where I’ll dive deep into how I run my agency and then also answering any questions or helping with proposals etc that yall might have in real time - Q&A: this is a free for all for you to come And have me cornered to ask any and all questions All of these will be recorded and saved in the classroom! Please let me know what else you’d like to see and how I might make this community amazing. Looking forward to it. — Tanner

When most people hear the word automation, they think of something simple: a repetitive task that gets done automatically so they can save time. And honestly? That part is true. At its most basic level, an automation is a system that takes Task A, applies a defined set of rules, and reliably delivers Result B — every time, without human intervention. No breaks. No forgetting. No inconsistency. That alone already has value. But that definition barely scratches the surface of what automation really means in a business context. Automation Is Not the Tool — It’s the Outcome A common mistake businesses make is focusing on the tool instead of the outcome. Automation is not: - n8n - Zapier - Make - AI agents - APIs - Scripts Those are just instruments. Automation is the intentional design of a process that removes friction, reduces waste, and produces consistent results aligned with business goals. The real question is never: “Can this be automated?” The real question is: “What business result do we want to achieve, and how do we design a system that gets us there reliably?” What Actually Happens Behind the Scenes This is where we come in. We are not “button clickers” or “workflow builders.” We are architects of business flow. Our job is to take something that exists in your business — an idea, a task, a process, a bottleneck, or even pure chaos — and design a structured path from Point A to Point B, based on your desired outcome. That “thing” can be: - A lead coming in - An email being received - A form submission - A customer action - A manual internal process - A recurring operational chore - A creative workflow - A reporting requirement Once the goal is defined, we design the logic, rules, validations, fallbacks, and integrations that make the system work reliably in the real world, not just in theory. The “Magic” Is Just Well-Designed Systems From the outside, automation often looks like magic. An email triggers a workflow. A lead gets scored automatically. A report is generated and sent. A video is created, branded, and posted across multiple platforms. A customer receives the right message at the right time.

For anyone planning to start charging for automations, this is a good place to start.Review the included documents and make sure they fit your situation.They’re meant to protect you and support you long-term. And as always, feel free to ask me anything. I’m here to help. Yes, they are .md files .md files are txt files, but you all already know that.

n8n Workflow Prompt Here is the master prompt that I use for starting to create an n8n workflow Feel free to modify it and add and remove things you think are and aren't necesarry. And note that I said starting. Because from there, I continue to build exactly what the client wants. AI and especially claude.ai can give you great workflows, but always check the end workflow for any mistakes that the AI might have done. n8n v2 Workflow Creation – System Prompt You are an n8n v2 expert. Your role is to design, validate, and document the automation I describe. Core Rules (Must Follow) - Use only verified, existing n8n v2 internal nodes - Use and verify the nodes from https://docs.n8n.io/integrations/builtin/node-types/ - Do NOT use Function nodes - Use Code nodes instead of Function nodes - Never invent node names, operations, credentials, or features - If you are not 100% sure a node or operation exists, do not use it - Prefer core n8n nodes whenever possible - Double-check the final workflow before presenting it If required information is missing, ask for clarification. Do not guess. Do not fill gaps. Required Deliverables (Mandatory) You must produce the following files: 1. A valid n8n workflow JSON file 2. A README.md file 3. An INSTALL.md file If any file cannot be produced, clearly explain why. Workflow Output Requirements - Verify every node before inclusion - Validate the workflow logic end-to-end - Do not include unused or unnecessary nodes - Ensure the workflow matches exactly what was requested Writing Style Rules - Be direct and concise - Use natural, plain language - Avoid marketing or hype - Avoid filler words and clichés Do NOT use phrases like: - “Let’s dive into…” - “Game-changing” - “Unleash your potential” Use instead: - “Here’s how it works.” - “This step does the following.”

🚨 A quick security reminder about automation workflows Don’t run workflows from strangers without inspecting every single node first. Whether it’s an n8n workflow, Make scenario, Zap export, or a random JSON someone drops in a Discord or Skool post — blindly importing and running automations is risky. There are bad actors out there. Some are obvious. Some are very good at hiding what they’re doing. I’m sharing workflows to help people learn and move faster — but you should still verify everything before you run anything. Why this matters Automation tools usually have deep access to: - APIs - Databases - Credentials - File systems - Webhooks - Internal business data A single hidden node can: - Exfiltrate credentials - Send your data to a third-party server - Create hidden webhooks - Write or delete database records - Trigger actions on a schedule you never notice And the scariest part? ⚠️ It can look completely harmless at first glance. Good security practices (please don’t skip these) 1️⃣ Inspect every node — no exceptions - Open each node - Check URLs, endpoints, headers, payloads - Look for unfamiliar domains or IPs - Be suspicious of “utility” or “helper” nodes 2️⃣ Verify the source - Who posted it? - Do they explain what it does and why? - Does the workflow come with context or documentation? - Anonymous drops = 🚩 3️⃣ Never import with credentials pre-attached - Remove all credentials before testing - Re-add your own manually - Never trust “ready-to-run” workflows with keys baked in 4️⃣ Test in a sandbox first - Use a dev instance - Use test APIs / fake data - Never run unknown workflows in production first 5️⃣ Watch for outbound traffic - HTTP Request nodes - Webhooks - “Logging” endpoints - Anything sending data “for analytics” If you don’t recognize the destination — investigate. 6️⃣ Least-privilege access - Use limited API keys - Separate prod vs dev credentials - Rotate keys regularly