n8n

Action

Action Nodes, Triggers and Functions

Action

For the sake of clarity, let’s consider any node that performs an action on a given service or platform as an “action plugin.” The exact categorization might vary based on the way n8n continues to evolve.

These nodes perform an operation like sending an email, adding a database record, or making an HTTP request.

• CRUD Operations : Most service-based nodes in n8n have Create, Read, Update, and Delete operations. For instance:

  • Airtable : Actions like “Append”, “List”, “Read”, and “Update”.
  • MongoDB : Operations like “Insert”, “Find”, “Update”, and “Delete”.

• Messaging Actions : For nodes that allow sending messages or notifications.

  • Slack : Send message, Invite user, etc.
  • Telegram : Send message, Send photo, etc.

• File Manipulation Actions : Nodes that allow file uploads, downloads, and manipulation.

  • FTP : Upload, Download, Rename, etc.
  • Google Drive : Create, Download, List, etc.

• Utility Actions : Various utilities or actions that might not fit into typical CRUD operations.

  • HTTP Request : Make a custom HTTP request.
  • Execute Command : Run a custom shell command.
  • Spreadsheet File : Read, Write operations on spreadsheets.

• Data Transformation & Manipulation : Although not directly “actions” on other services, these nodes perform actions on the data within the workflow.

  • Set : Set or overwrite values.
  • Move Binary Data : Move binary data between properties.
  • Rename : Rename keys.

• Flow Control Actions:

  • SplitInBatches : Splits items in batches for parallel processing.
  • Merge : Merge multiple streams of data.
  • NoOp : Do nothing (used for controlling flow or debugging).

• External Integrations: Almost every integration with an external service will have specific actions unique to that service.

  • GitHub : Create issue, Get repository, etc.
  • Twilio : Send SMS, Make Call, etc.
  • Shopify : Create product, List orders, etc.

Action Examples

• Slack - Send Message:

  • This action allows you to send a message to a specific Slack channel or user.
  • Inputs might include the channel ID, message content, attachments, etc.

• HTTP Request:

  • Lets you make a custom HTTP request to any API. Inputs include the request method (GET, POST, PUT, etc.), URL, headers, query parameters, and body.

• Google Drive - Create:

  • Create or upload a new file to Google Drive. Inputs can be the file data, folder ID (if you’re placing it in a specific folder), and other metadata.

n8n Functions

Function nodes in n8n allow users to execute custom JavaScript code to manipulate or process data within a workflow. They provide flexibility by enabling bespoke data transformations or logic not covered by default nodes.

n8n Functions

• These plugins allow for custom JavaScript code to be run within your workflow, offering a great deal of flexibility.

• Example: The ‘Set’ plugin allows you to set and manipulate data at any point in your workflow, ensuring the data flows precisely as you desire.

n8n Supabase Notes

n8n Supabase Integration

n8n Supabase

These are general notes for the integration of n8n and supabase.

Supabase Cache

We will be using n8n to handle the redis cache from Supabase. The goal would be to migrate the data closer to our edge containers before migrating to production. For the initial development, we will start with n8n and eventually shift towards migrating the logic and code flow to a Rust-based microservice.

n8n Redis

For storage of the data, we will be using redis, so make sure that you have that integrated. In addition, some of the general logic for the basic n8n will be provided here in the notes.

Supabase Workflow Key Sheet

username can be called via {{ $('Init').item.json.username }}. action can be called via {{ $('Init').item.json.action }}.

Plugins

n8n plugins

Plugins

Hello my dear fellow automation enthusiasts!

In our previous articles, we introduced you to the magic of n8n—a node-based, open-source tool that has been redefining the boundaries of workflow automation. But what makes n8n truly stand out in the bustling crowd of automation platforms? It’s their vibrant and versatile plugin ecosystem. Just like a painter needs more than just a basic palette to create masterpieces, n8n offers a vast range of plugins to help customize your workflow and integrate seamlessly with myriad tools. Let’s dive into this colorful world and explore the different types of plugins n8n offers.

Data Transformation Plugins

What are they? Often, data doesn’t come in the format we desire. These plugins reshape, transform, and mold data to fit our requirements.

Example: The ‘Spreadsheet File’ plugin reads data from an XLS or CSV file and turns it into a usable JSON format for further processing.

Authentication Plugins

What are they? Security first! These plugins enable secure connections between n8n and external services.

Example: The ‘OAuth2 API’ plugin provides a mechanism to securely authenticate with services using the OAuth2 protocol.

Service Integration Plugins

What are they? n8n’s true power lies in its ability to integrate with a plethora of services. These plugins facilitate those integrations.

Example: The ‘Slack’ plugin lets you send messages, upload files, and interact with Slack directly from your n8n workflow.

The brilliance of n8n lies not just in its foundational architecture, but in its dynamic ecosystem of plugins. They enable users to customize, expand, and enhance their automation dreams. With a constantly growing community, expect to see more innovative plugins emerge, each widening the horizons of what’s possible with n8n.

Keep automating and stay tuned for our next dive into the wonderful world of n8n!

n8n Triggers

These nodes start a workflow. For example, receiving a webhook or detecting a new email.

Trigger

Can be referenced as Trigger Nodes, Trigger Plugins, ect…

As we venture deeper into the labyrinth of n8n’s powerful ecosystem, it’s hard not to be intrigued by its trigger plugins. Acting as the heartbeat of any workflow, these plugins are the gatekeepers, deciding when a workflow should spring to life. For both developers and tech enthusiasts, understanding these triggers can be the key to maximizing n8n’s potential. Remember that triggers can be a reaction based on an event or condition!

There a couple different ways to activate the triggers, these below are the main ways.

• Webhook Trigger

  • A listener waiting for an external input. Once an external service sends data to the specified URL, the magic begins.
  • Use Case: Imagine a content management system notifying n8n every time a new article is published, enabling a chain reaction of automated tasks like social media postings.

• Interval Trigger

  • Time-based triggers that execute workflows at regular intervals.
  • Use Case: You could use this to periodically fetch and backup data from a database, ensuring you have timely backups without manual intervention.

• Cron Job Trigger

  • Advanced time-based triggers allowing complex schedules. Using cron syntax, one can specify intricate timings.
  • Use Case: A journalist might use this to run a workflow that compiles daily news from various sources at 7 am every weekday.

• Startup Trigger

  • This trigger activates a workflow as soon as n8n starts. It’s a one-time trigger for initializing processes.
  • Use Case: A developer could utilize this to initialize certain environment variables or to send notifications about system startups.

• MQTT Trigger

  • It listens for messages from an MQTT broker—a communication protocol for IoT devices.
  • Use Case: Imagine your smart thermostat triggering a workflow in n8n whenever your room temperature crosses a certain threshold, prompting automated alerts or actions.

• External Trigger

  • A plugin that allows other automation platforms, like Zapier, to initiate workflows in n8n.
  • Use Case: This would be beneficial for those transitioning from other platforms or aiming to integrate n8n with existing setups.

Intricacies and Insights

The power of trigger plugins lies in their versatility. For the developer, they offer a range of options to kickstart intricate automation. For the journalist or business user, they paint a picture of how automated actions can originate from a plethora of events, whether they’re time-based, external signals, or even IoT messages. In essence, n8n’s trigger plugins embody the principle that in the realm of automation, starting right is half the battle won.

J1

Journal Entry 1

J1

These are the collection of notes for N8N.

Need to migrate some of the concepts over and start to automate the pull and push commands using n8n.