Made this one because a member in here asked for it, the only n8n tutorial you need. Three builds from scratch in a single video. A daily weather email, a client intake router that reads revenue and sends personalized replies down the right path, and an AI crypto research agent that pulls live data, runs GPT analysis, and logs everything to a sheet on autopilot. n8n is the workflow backbone underneath almost everything we build in OpenClaw, the piece that connects your tools, fires on schedules, and moves data between systems so OpenClaw can actually do the thinking on top. Most of the client builds people are shipping with OpenClaw lean on both, and if your skills are solid but the plumbing around them keeps breaking, this video patches that side of the stack. Workflow JSONs for all three builds are in the classroom, import them, swap your credentials, done. Go watch it and tell me what you'd want to wire into your OpenClaw setup first.

How do I setup and structure OpenClaw I want it to handle: - decisions - ideas → experiments - daily priorities - reflection

HEY GUYS, since @Eddy H mentioned this issue with spawning sub agents and since I had the same issue a couple of days ago, I wanted to share this SUB AGENT DELEGATION RULE prompt to send your bot. This pretty much fixed the issue for me. If you encounter and further problems of for example, your bot spawning an agent and the agent not being able to complete a task due to context being full, specify to your bot to spawn more agents when needed and save this information in the delegation rule: give your bot this exact command: ''follow this Sub-Agent Delegation Rule every session and always apply before answering: If a task takes more than 10 seconds to complete, spawn a sub-agent to handle it. Don't block the main session. Why: I need to stay available. While a sub-agent researches, builds, or processes something, I can keep chatting with you or spin up other sub-agents in parallel. How it works: • Quick answers, lookups, small edits → do it directly • Research, builds, long file operations, API calls → spawn a sub-agent • Multiple tasks? Multiple sub-agents. Run them in parallel. Always: • Tell me what sub-agent you're spinning up and what it's doing • Ping me when it's done with the result • Keep the main thread responsive Save this rule and apply it every session.''

I watched this video and wonder how complex will this multi agent setup https://youtu.be/VCK06OycE5Q?si=KG22tco3zye5m4hJ