Introduction

In this short article, we will cover the main features of working with automated workflows using N8N.io.

We will highlight the main features of working with N8N workflows and look at a sample workflow I created to help you better understand how to work with them.

In a future article, we will explore the Trigger.dev library which can be used to enhance your experience with N8N workflows in a Next.js application.

What are N8N Workflows?

Unlike AI agents, N8N workflows are static in nature. From the trigger node to the last node, automated workflows follow the exact same execution pattern.

AI agents are dynamic in nature. They may have access to the same tooling, LLMs, and other resources, but the results vary each time the same task is being completed.

N8N Workflow Nodes

N8N workflows are an interconnected system of nodes. Each node inside a N8N workflow fulfills a unique purpose that helps to serve the overall goal of the workflow.

The following list highlights important nodes that you will use in workflow development:

Trigger Nodes — Start a workflow based on an event, schedule, web hook, or manual execution.
Action Nodes — Perform operations in external databases and services.
Core Nodes — Built-in utility nodes for manipulating data, merging inputs, and other common workflow operations.
Flow Control Nodes — Control the execution path of a workflow using conditions, branching, looping, and error handling.
Data Transformation Nodes — Modify, format, convert, filter, and restructure data between workflow steps.
Code Nodes — Execute custom JavaScript or Python when built-in nodes are insufficient.
HTTP & API Nodes — Connect to virtually any REST or GraphQL API, including sending requests and processing responses.
Database Nodes — Read, write, update, and query data from SQL and NoSQL databases.
File & Binary Nodes — Handle files, images, PDFs, spreadsheets, binary data, and file conversions.
Communication Nodes — Send notifications, emails, messages, and interact with chat or collaboration platforms.
AI Nodes — Integrate with LLMs, vector databases, AI agents, and memory.
Authentication & Credential Support — Use secure credentials such as API keys, bearer tokens, and environment variables to access external services.
Community Nodes — Extend n8n with additional integrations and functionality through community-developed node packages.

These are the main N8N nodes you will encounter in development.

N8N Workflow Setup Options

When working with N8N workflows, you have several setup options at your disposal.

The most common way to get started on N8N workflows is by using the official N8N Docker image.

N8N comes with its own official published image that you can fetch from DockerHub and run a container instance of that image locally on your machine.

The second option is to install the official N8N NPM package from the NPM registry locally on your computer.

Simply invoking n8n in your terminal will open the N8N workspace on localhost:5678.

Lastly, if you do not want to manage any infrastructure on your own, N8N cloud is the way to go. You can simply sign up and subscribe to any of their paid plans.

N8N Workflow Example

You can follow along by cloning this GitHub repository. The directory we will be working with is located here /demos/Demo81_N8N_Workflows/n8n_workflows.

In this section, we will cover a workflow that I personally created for the purposes of learning.

The following image captures the purpose of this workflow /demos/Demo81_N8N_Workflows/n8n_workflows/Daily_Crypto_Market_Update_Email.PNG:

No Image Found — Simple workflow gathers cryptocurrency data and uses an AI agent and Resend node to send detailed emails

The workflow is based on a scheduled trigger node. This node automatically runs the workflow at a set schedule and starts out by retrieving cryptocurrency market data using APIs with the help of the HTTP node.

These are authenticated API calls so authentication must be provided within the HTTP node itself in the form of an API key.

The data from the response is processed and cleaned up using code function nodes and merged together as a feed for an AI agent node.

AI agent nodes inside N8N workflows are complex. For this example, I did not add any external tooling or memory storage (you have the option of selecting and connecting to a database).

The AI agent node is given a prompt to help write an email message which contains a detailed paragraph explaining the context of the incoming market data.

Finally, a plug-in node is used to send out the email containing the detailed information. I used the Resend plug-in node to send emails.

It is mandatory to provide the necessary authentication in plug-in nodes in order to use them.

You can view the exported N8N workflow in JSON format here. The JSON document is a very long read.

Conclusion

We did a deep dive into N8N workflows. We covered the main aspects of the N8N ecosystem and looked at a sample workflow that you can design on your own using different nodes such as the flow, code, merge, and plug-in nodes.

In the list below, you will find links to the official N8N docs and the GitHub repository containing the exported N8N workflow in JSON format:

I hope you found this article helpful and look forward to more in the future.

Thank you!

TL;DR on Automated Workflows with N8N