NodeRecipe.

Practical n8n guides with test versions and results

n8n tutorials, workflow templates & AI-agent automation guides

Practical n8n tutorials, ready-to-use workflow templates, and AI-agent automation guides. Self-hosting, integrations, and real-world recipes.

Browse the 21 guides9 free templates
n8n execution view: a Webhook feeding an OpenAI node named Classify, a Code node Normalise Label, then a Switch node Route By Category fanning out to five branches for sales, support, billing, spam and a review queue
Not a diagram — this is our classify-and-route workflow in n8n's execution view, on the run where a prize scam went to Spam and “What's the weather like in Lisbon?” came back as other and fell through to Review.
21
guides, dated and corrected in place when n8n changes
9
workflow templates, MIT licensed, no email gate
0
affiliate links and sponsored placements

Why these guides spend so long on what goes wrong

Because that is the part the documentation leaves out. Below is n8n refusing to test-run a published Slack workflow — a real limit, with a real message, that appears nowhere in the docs. We found it by trying it, and now it's in the Slack guide instead of costing you an afternoon.

The n8n editor showing a Slack Trigger connected to a Handle Event node, with a red error toast reading: Problem running workflow — Because of limitations in Slack Trigger, n8n can't listen for test executions at the same time as listening for production ones. Unpublish the workflow to execute.
n8n 2.33.7 refusing a test run on a published Slack Trigger workflow. The message is accurate and undocumented.

The same rule applies to every article here: how these get written, and how the site makes money.

Choose a starting point

Build an AI workflow

For a single classification or extraction call, start with OpenAI integration. Use the chain and parser guide to understand structured output. If the model needs to choose tools, read the agent guide.

For answers grounded in your documents, follow the RAG walkthrough. For connecting tools over MCP, first distinguish the three MCP features.

Connect services and handle failures

Start with webhook requests and responses, then choose a destination: spreadsheet rows, Notion pages, or transactional email.

Use Slack or Telegram for notifications. If an expected run never appears, follow the trigger troubleshooting sequence before adding retries.

New to n8n? Build your first workflow before connecting a production service.

Latest guides