Module 3 Lesson 2: Core Action Nodes

Once your workflow is triggered, it needs to Do something. Action nodes are the verbs of the n8n language.

1. The HTTP Request Node (The "Universal" Node)

If an app doesn't have a native node in n8n, you use the HTTP Request node. It allows you to talk to ANY API in the world.

• You define the URL, the Method (GET/POST), and the Headers (API Keys).

---

2. The SET Node (The "Renamer")

The Set node is used to "Clean up" your data.

• Removing sensitive data: If you get a user's whole profile but only want their email, use the Set node to delete everything else.
• Renaming fields: Change fname to first_name so it matches your CRM.

---

Visualizing the Process

graph TD
    Start[Input] --> Process[Processing]
    Process --> Decision{Check}
    Decision -->|Success| End[Complete]
    Decision -->|Retry| Process

---

3. The Wait Node (The "Patient" Node)

Sometimes you need to pause.

• "Send email 1 -> Wait 2 days -> Send email 2."
• This allows you to build complex multi-day marketing drips or follow-up cycles.

---

4. The Crypto Node (Security)

Automation often involves sensitive data. The Crypto node allows you to:

• Sign a message to prove it's from you.
• Hash a password using MD5, SHA256, etc.
• Encrypt a field before saving it to a public Google Sheet.

---

5. The Read/Write File Node

These nodes interact with your server's hard drive (or Docker volume).

• Read Binary File: Load an image from a folder.
• Write Binary File: Save a report you just generated.

---

Exercise: The Action Challenge

1. Add an HTTP Request node. Point it to https://jsonplaceholder.typicode.com/todos/1.
2. Execute the node. What is the "Title" of the todo item?
3. Add a Set node after it. Create a new field called status with the value COMPLETED.
4. Delete the original id and userId fields using the Set node's "Keep only set" toggle.
5. Why would you use the Wait node instead of just writing a sleep() function in code?

---

Summary

Action nodes are where the "Value" is created. By knowing which node to reach for—whether it's a specialized CRM node or a generic HTTP request—you become a faster and more efficient automation engineer.

Next Lesson: Power to the coder: The 'Execute Command' and 'Code' Nodes.