n8n is a way to draw “when this happens, do these steps.” The first workflow should be boring: one trigger, a clear input, one decision, one destination, and a message when it breaks.
Pick the task
Automate work that happens at least three times a week and does not need a fresh judgment each time. Form to spreadsheet, a daily summary into chat, mail with a label into a to-do. Do not start with refunds or production database merges.
Four stages
| Stage | Does | Does not |
|---|---|---|
| Trigger | Manual, clock, or webhook | Hide the time zone |
| Fetch | Read the raw row or payload | Decide yet |
| Decide | One condition | Five rules in one expression |
| Write | Save the result and notify | Retry a payment blindly |
A green node is not a business success. APIs return HTTP 200 with an error in the body. Check that field.
Store credentials in n8n’s credential store, one per service. Retry reads. Do not retry sends unless a second send is harmless. On failure, notify a person with the workflow name, the node, and an id such as an order number. Pause the trigger if the same error repeats, then replay saved inputs.
When to leave the diagram
Long loops, code review, and repo secrets belong in GitHub Actions. n8n can receive the event and post the alert. For Make versus n8n, read Make or n8n.
Before you enable the schedule, run three cases: a good row, a missing field, and a downstream failure.