How to Build Your First n8n Automation in 30 Minutes

If you’ve been looking for a practical n8n automation tutorial that skips the theory and gets you to a working workflow, this is it. n8n is an open-source automation platform that connects your tools, runs logic, and handles repetitive work without you writing a single line of code — unless you want to. In 30 minutes you’ll have a real workflow running: one that monitors an RSS feed, summarises new items using AI, and posts the result to Slack. Everything here is repeatable. Once you understand the pattern, you can apply it to almost any integration problem you face.

What Is n8n and Why Should You Care?

n8n is a workflow automation platform built for people who want real control over their automations. Unlike Zapier or Make, it is open source and self-hostable — which means your data stays on your infrastructure and you are not paying per-task pricing as you scale.

• Open source. The code is public, auditable, and free to self-host. No vendor lock-in.
• Visual workflow builder. Nodes connect to each other on a canvas. You see the data flowing between steps in real time.
• 600+ integrations. Slack, Notion, Google Sheets, OpenAI, Airtable, GitHub, HubSpot — most tools you use are already supported out of the box.
• Self-hostable. Run it on your own server via Docker or use the managed n8n Cloud offering. You choose.
• AI-native. n8n has first-class support for AI agent nodes, LLM integrations, and multi-step AI workflows. It is not bolted on as an afterthought.

For anyone building automation pipelines, content workflows, or internal tooling, n8n is one of the most capable platforms available. It rewards investment — the more you use it, the faster you can ship new automations.

What You Will Need

This tutorial is beginner-friendly. Here is everything you need before you start:

• A free n8n Cloud account (or Docker if you prefer self-hosted)
• An OpenAI API key (or a Claude API key if you prefer Anthropic)
• A Slack workspace where you can create a bot and post messages
• An RSS feed URL — any news feed or blog will work
• 30 minutes

You do not need to know how to code. You do not need a server. The cloud version of n8n handles infrastructure for you.

Step 1: Set Up Your n8n Instance

For your first automation, use n8n Cloud. Go to n8n.io, create a free account, and you will have a working n8n instance in under two minutes. No Docker, no server configuration, no port forwarding.

If you already run Docker and prefer self-hosting, pull the n8n image and run it locally. The command is straightforward and the n8n documentation covers it in detail. For this tutorial the interface is identical regardless of how you host it, so either path works.

Once you are logged in, you will land on the n8n dashboard. This is where all your workflows live. Create a new workflow by clicking the button in the top right. You will see a blank canvas with a single “Start” node. This is your workspace.

Step 2: Create Your First Workflow

The workflow you are building has three steps: trigger, process, act. Concretely:

• Trigger: A new item appears in an RSS feed.
• Process: Send the item title and description to an AI model and ask it for a one-paragraph summary.
• Act: Post that summary to a Slack channel.

This is a real, useful workflow. I use a version of this to monitor industry news and surface relevant items to a Notion database without manually checking feeds. Once you understand the three-node pattern, you can swap in any trigger, any processing step, and any output destination.

Delete the default Start node. You will replace it with a proper trigger in the next step.

Step 3: Add a Trigger Node

Click the “+” button to add a node. Search for “RSS Feed” and select it. This node polls an RSS feed on a schedule and fires the workflow whenever a new item appears.

Configure the RSS Feed node:

• Feed URL: Paste in the RSS feed you want to monitor. Hacker News, your favourite tech blog, or any feed you check manually today.
• Polling interval: Set how frequently n8n should check for new items. Every 15 minutes is a reasonable default for most use cases.

Click “Test step”. n8n will fetch the feed and show you the data from the first item — title, link, description, published date, and any other fields the feed includes. This is the data that will flow through the rest of your workflow. Get familiar with the field names; you will reference them in the next step.

Step 4: Add an AI Node

Click “+” after the RSS node to add the next step. Search for “OpenAI” (or “Anthropic” if you are using Claude). Select the “Message a Model” operation.

Configure the AI node:

• Credential: Add your API key. n8n stores it securely and you only do this once.
• Model: GPT-4o-mini works well for summarisation tasks and is cost-effective at volume. Claude Haiku is a strong alternative.
• Prompt: Write a clear instruction. Something like: “Summarise the following article in two sentences. Title: {{ $json.title }}. Description: {{ $json.description }}”. The double curly brace syntax pulls data from the previous node automatically.

Click “Test step”. You should see the AI’s response — a two-sentence summary of the RSS item — in the output panel. If the summary looks thin, check that the description field actually contains content from your feed. Some feeds only include titles in the RSS output; if that’s the case, include the link and use a web scraping node before the AI step.

Step 5: Add an Action Node

Click “+” after the AI node. Search for “Slack” and select the “Send a Message” operation.

Configure the Slack node:

• Credential: Connect your Slack workspace. n8n will walk you through creating a Slack bot with the right permissions.
• Channel: Enter the channel name where summaries should be posted. Create a dedicated channel like #ai-digest to keep things tidy.
• Message text: Compose the message using data from earlier nodes. A clean format: "*{{ $json['title'] }}*\n{{ $node['OpenAI'].json['message']['content'] }}\n{{ $json['link'] }}" — gives you the title in bold, the AI summary, and the original link.

If you prefer Notion over Slack, the pattern is identical — swap the Slack node for a “Create Database Item” Notion node and map the fields to your database properties. Email works the same way via the Gmail or SMTP nodes.

Step 6: Test and Activate

Click “Test workflow” in the top bar. n8n runs the entire chain — RSS fetch, AI summarisation, Slack post — and shows you the output at each step. Check each node’s output panel and confirm the data looks right.

Common errors at this stage:

• Authentication failed: Double-check your API keys and Slack bot permissions. The most common cause is a missing OAuth scope on the Slack bot.
• Empty AI response: The prompt references a field that is empty or misnamed. Check the RSS node output and confirm your field names match exactly.
• Slack channel not found: Make sure the bot has been invited to the channel. Slack bots cannot post to channels they are not members of.

Once the test run completes without errors, click “Activate” in the top right. The workflow is now live. n8n will poll the RSS feed on your chosen interval and run the full chain automatically whenever a new item appears. No intervention required.

Where to Go From Here

You now have a working three-node automation. Here is where most people take it next.

• Community templates. n8n has over 6,100 community-built workflow templates. Browse them at n8n.io/workflows — there is almost certainly a template for the next workflow you want to build.
• AI workflow chaining. Add a second AI call after the first. The output of one model becomes the input of the next — classify, summarise, translate, score. Chained AI nodes let you build surprisingly sophisticated processing pipelines.
• AI agent nodes. n8n has a dedicated AI Agent node that gives the model tool access and lets it plan multi-step workflows autonomously. This is the bridge between simple automation and agentic AI.
• Webhook triggers. Replace the RSS trigger with a Webhook node and your workflow becomes an API endpoint. Send data to it from any external system and the workflow fires instantly.
• Error handling. Add an Error Trigger workflow that catches failures and sends you a Slack alert or creates a Notion task. Production automations need error visibility.
• Notion as your operating system. The most powerful setup I run combines n8n with a structured Notion workspace — automations feed data into Notion databases, Notion acts as the single source of truth, and dashboards surface what needs attention.

If you want to see how I use n8n alongside Notion for my entire operating system, check out the templates — pre-built Notion systems designed to work with automation pipelines from day one.