This community is growing faster than ever and I am committing to know *your* needs and wants. Why are you here? What do you want (big picture)? What is the 1 thing stopping you from building your dream *right now*?

Would love some feedback on this. If you need a deepseek API key you can sign up and add $2 and it will last you a really long time - if you don't have $2, that's okay, just DM Tanner and he'll hook you up. https://cfomodz.github.io/deep-task/

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.”

I ran into an issue where my workflow kept failing because the node expected a string but received an object. Solution: - Added a Set node to stringify the JSON - Verified output in execution logs before mapping Sharing in case it helps someone else 👍

I usually think about workflows like this: Trigger → Process → Output When something breaks, it’s almost always in the Process step due to data shape issues. Stepping through each node with execution logs usually makes the issue obvious.