komasu Tools
English
English 日本語 Deutsch Français Español Italiano Nederlands Português 한국어 繁體中文

n8n Tutorial (2026): Build Your First Workflow Step by Step

By komasu team · Updated · Facts checked · 8 min read

komasu Tools is supported by readers like you. We may earn an affiliate commission when you purchase through our links, which enables us to offer our research for free. How we make money

A published n8n Cloud workflow that runs on a schedule, fetches data from an API, keeps only the items you care about and posts them to a Slack channel.

Try n8n for free

What you will build

In this tutorial you build a small but realistic automation on n8n Cloud. Every morning it fetches a list of records from an API, keeps only the ones that match a condition, and posts each match to a Slack channel. Think of new orders above a certain value, open support tickets, or tasks due today.

The workflow uses four nodes, all from n8n's official documentation:

  1. Schedule Trigger starts the workflow at a set time.
  2. HTTP Request calls the API and returns its data.
  3. Filter keeps only the items that meet your condition.
  4. Slack sends a message for each remaining item.

Along the way you will learn the core n8n ideas: a workflow is the whole automation, a node is one step, and data moves between nodes as a list of items. An execution is one run of the whole workflow, which is also how n8n Cloud counts usage.

Before you start

You need three things:

If you prefer email, you can swap Slack for the Gmail node in Step 5. The rest stays the same.

If you are still deciding whether n8n is the right tool, read our n8n review first.

Step 1: Create a new workflow

Log in to n8n Cloud. In the left menu, select Personal, then Create workflow. You now see an empty canvas, the area where you place and connect nodes.

Give the workflow a clear name, such as "Daily filtered report to Slack". Names matter once you have dozens of workflows, and they show up in error alerts.

n8n also offers a built-in Assistant that can build a workflow from a chat prompt. It is useful later, but building by hand the first time teaches you how the pieces fit together.

Step 2: Add a Schedule Trigger

Every workflow starts with a trigger node. Select Add first step, then choose On a schedule. This adds the Schedule Trigger node.

In the node settings, keep the interval at days and set Trigger at Hour to the time you want, for example 8am. The schedule uses the timezone of your n8n instance, so check that it matches where you are.

Rename the node to something descriptive, such as "Every day at 8 AM". Close the panel to return to the canvas.

Step 3: Fetch data with the HTTP Request node

Select the + button on the right side of the trigger node. In Search nodes, type "http" and choose HTTP Request.

Set the method to GET and paste your API's address into the URL field. If the API needs authentication, choose it under the authentication settings and store the key as a credential. Credentials are saved separately from the workflow, so the key does not appear in the node itself and can be reused.

Now select Execute step. n8n calls the API once and shows the result in the output panel. If the response is a list, you should see several items. If your list is nested inside a field of a single object (for example data or results), add a Split Out node after this one and point it at that field so each record becomes its own item.

Rename the node to something like "Get records". Running a step and looking at its real output before moving on is the single most useful habit in n8n.

Step 4: Keep only what matters with the Filter node

Add a node after HTTP Request and search for Filter. According to n8n's docs, the Filter node passes on items that meet a condition and drops the rest.

Set up the condition:

  1. In the first value field, reference a field from the input. Open the input panel on the left and drag the field (for example status or amount) into the value box. n8n writes an expression such as {{ $json.status }}, which it replaces with each item's real value at run time.
  2. Use the data type dropdown to pick the type and comparison, such as String with "is equal to", or Number with "is greater than".
  3. Type the value to compare against, such as open or 100.

To add more rules, select Add condition and choose AND (all conditions must match) or OR (any condition can match). You cannot mix AND and OR inside one Filter node. Under options, Ignore Case makes text comparisons case insensitive, and Less Strict Type Validation helps if you see a "wrong type" error.

Select Execute step again. The output should now contain only the matching items. If it is empty, check your condition against the input data before moving on.

Step 5: Post each match to Slack

Add a node after Filter and search for Slack. For the action, choose the Message resource with the Send operation, which posts a message to a channel.

Next, connect your Slack account. The Slack node supports OAuth2 and Access Token authentication. Create a new credential from the node and follow the steps on n8n's Slack credentials page. If you set up your own Slack app, make sure it has the scopes the docs list for sending messages.

Then choose the channel and write the message text. Mix fixed text with expressions from the input, for example:

New item: {{ $json.name }} (status: {{ $json.status }})

Use the field names from your own data. n8n runs the Slack node once per incoming item, so three filtered items produce three messages.

Select Execute step and check the Slack channel. When the test messages look right, rename the node to "Post to Slack".

Step 6: Test the whole workflow and publish it

So far you have tested one node at a time. Now select Execute under the canvas to run the whole workflow from the trigger. Each node should show a green check mark when it succeeds.

A tested workflow does not run on its own yet. To switch the schedule on, select Publish in the canvas header. From now on, n8n starts the workflow automatically at the time you set in Step 2, and each run counts as one execution.

If you change the workflow later, remember to publish again so the live version picks up your edits.

Step 7: Check runs and add an error alert

Open the workflow's executions tab to see past runs, whether each one succeeded, and the data that passed through each node. This is where you look first when something goes wrong.

For a safety net, create a second workflow that starts with the Error Trigger node and sends a Slack message or email with the error details. Then open your main workflow, go to Options > Settings, and choose that workflow under Error workflow. According to n8n's docs, the error workflow receives the failed execution's ID, the error message and the last node that ran, and one error workflow can serve many workflows.

Step 8 (optional): Run n8n yourself with Docker

n8n Cloud is the easiest way to start, but you can also self-host the free Community Edition. Its license is the Sustainable Use License, which allows internal business, personal and non-commercial use. The n8n docs warn that self-hosting requires technical knowledge, and that mistakes can lead to data loss, security issues and downtime.

For a local test, the docs describe this setup with Docker Desktop installed:

  1. Create a volume so your data survives restarts: docker volume create n8n_data
  2. Start n8n with the official image, mapping port 5678 and mounting the volume: docker run -it --rm --name n8n -p 5678:5678 -e GENERIC_TIMEZONE="<YOUR_TIMEZONE>" -e TZ="<YOUR_TIMEZONE>" -e N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true -v n8n_data:/home/node/.n8n n8nio/n8n
  3. Open http://localhost:5678 in your browser.

Replace <YOUR_TIMEZONE> with a timezone name such as America/New_York. For anything beyond a local test, n8n's docs recommend the Docker Compose installation instead, and you are responsible for updates, backups and HTTPS. Some team features, such as projects and SSO, are not part of the Community Edition.

Common mistakes

Next steps

You now have a published workflow that runs every morning and reports only what matters. From here, try adding an If node to send different messages for different cases, or replace Slack with Gmail for an email digest. n8n's template library is also a good place to see how others structure similar flows.

If you want to compare n8n with other tools before building more, read Make vs n8n and Zapier vs n8n, or follow our Make tutorial to build the same kind of workflow there.

Keep building with n8n

Frequently asked questions

Do I need to know how to code to follow this tutorial?

No. Every step uses n8n's visual nodes and form fields. You will type a few short expressions, but no code.

Does the n8n Cloud trial cost anything?

According to n8n, the 14-day Cloud trial requires no credit card and includes Pro features with 1,000 executions. If you do not upgrade, the trial ends automatically.

How many executions does this workflow use?

One per run. n8n counts an execution as a single run of the entire workflow, regardless of how many nodes it has, so a once-a-day schedule uses about 30 executions a month.

What is the difference between Execute and Publish?

Execute runs the workflow once so you can test it. Publish makes it live, so the Schedule Trigger starts it automatically at the times you set.

Can I send an email instead of a Slack message?

Yes. Replace the Slack node with the Gmail node or another email node and map the same fields into the message.

Can I run this workflow on my own server?

Yes. You can self-host the n8n Community Edition with Docker, as described in the last step, and import or rebuild the workflow there.

See the update history of this article
  • First published.

komasu team

komasu is an independent developer in Japan that builds small software tools and runs its own business on automation and no-code products. We write research-led reviews: we read the documentation, pricing pages and public user feedback, score every tool on the same fixed criteria, and date every fact we state.

About · Methodology