n8n

You can make a workflow actually run and carry data forward.

1. 1Nothing runs without a triggerYou can apply this in a live incident: A workflow starts only when a trigger node fires.12m30xp
2. 2Trigger, action and flow nodesYou can apply this in a live incident: Triggers start execution.12m30xp
3. 3Items and jsonYou can apply this in a live incident: n8n passes arrays of items, each with a json object.12m30xp
4. 4ExpressionsYou can apply this in a live incident: Expressions are JavaScript inside {{ }}.12m30xp
5. 5CredentialsYou can apply this in a live incident: Credentials are stored separately from the workflow.12m30xp
6. 6Binary dataYou can apply this in a live incident: Files live under binary, not json.12m30xp
7. 7IF and SwitchYou can apply this in a live incident: IF has true and false outputs.12m30xp
8. 8Merge and WaitYou can apply this in a live incident: Merge waits for its configured inputs.12m30xp
9. 9Error workflowsYou can apply this in a live incident: A node can continue on fail and pass the error as data.12m30xp
10. 10Idempotent production runsYou can apply this in a live incident: Webhooks can fire more than once.12m30xp

You can operate workflows without turning them into unowned magic.

1. 1Environment and configurationYou can apply this in a live incident: $env reads environment variables.12m30xp
2. 2Rate limits and batchingYou can apply this in a live incident: SplitInBatches plus Wait is the usual throttle.12m30xp
3. 3Sub-workflowsYou can apply this in a live incident: Execute Workflow calls another workflow as a unit.12m30xp
4. 4Queue modeYou can apply this in a live incident: Queue mode separates webhook intake from workers.12m30xp
5. 5Executions and logsYou can apply this in a live incident: Execution data is how you debug a past run.12m30xp

You can pick HTTP, Set, Code and webhook nodes without guessing item shape.

1. 1HTTP Request nodeYou can apply this in a live incident: HTTP Request calls an arbitrary URL with method, headers and body you configure.12m30xp
2. 2Edit Fields (Set)You can apply this in a live incident: Edit Fields assigns or converts fields on each item.12m30xp
3. 3Code nodeYou can apply this in a live incident: Code runs JavaScript per item or once for all items.12m30xp
4. 4Webhook versus ScheduleYou can apply this in a live incident: Webhook starts a run when HTTP hits its path.12m30xp
5. 5Schedule timezoneYou can apply this in a live incident: Schedule uses a timezone you set on the node or instance.12m30xp
6. 6Webhook responseYou can apply this in a live incident: Respond to Webhook can answer immediately with a chosen status.12m30xp
7. 7Split OutYou can apply this in a live incident: Split Out turns an array field into multiple items.12m30xp
8. 8AggregateYou can apply this in a live incident: Aggregate combines items into one (or few) items.12m30xp
9. 9Loop Over Items (Split In Batches)You can apply this in a live incident: Split In Batches yields a batch, then you loop back with a Wait or the loop connector.12m30xp
10. 10Filter, Limit and Remove DuplicatesYou can apply this in a live incident: Filter keeps items that match a condition.12m30xp
11. 11Always Output DataYou can apply this in a live incident: Always Output Data emits an empty json item when there would be none.12m30xp
12. 12Pinned dataYou can apply this in a live incident: Pinned data substitutes a node's output while you build.12m30xp

You can read $json, lists and binary without mixing grains.

1. 1Expressions $json and $nodeYou can apply this in a live incident: $json is the current item.12m30xp
2. 2Item lists versus a single itemYou can apply this in a live incident: Most nodes run once per incoming item.12m30xp
3. 3Binary to JSONYou can apply this in a live incident: Binary is a sidecar on the item, not json.12m30xp
4. 4Execution orderYou can apply this in a live incident: n8n follows connections, not canvas x-position.12m30xp
5. 5Partial executionsYou can apply this in a live incident: You can execute a subset of the canvas while building.12m30xp
6. 6Pinning versus production dataYou can apply this in a live incident: Pinned payloads freeze a shape.12m30xp
7. 7Error output versus continueOnFailYou can apply this in a live incident: continueOnFail passes the failed item downstream with error data.12m30xp
8. 8Credential typesYou can apply this in a live incident: Each node family has credential types (OAuth2, header, basic, API key).12m30xp
9. 9Activation versus saveYou can apply this in a live incident: Save stores the graph.12m30xp
10. 10Wait and wait-for-webhookYou can apply this in a live incident: Wait can pause for a duration or until a webhook resume.12m30xp
11. 11AI nodes at a high levelYou can apply this in a live incident: n8n AI nodes wrap models, tools and memory as graph nodes.12m30xp

You can version workflows and survive community node upgrades.

1. 1Sticky notesYou can apply this in a live incident: Sticky notes are canvas annotations.12m30xp
2. 2Community nodesYou can apply this in a live incident: Community nodes are extra npm packages on the instance.12m30xp
3. 3Source controlYou can apply this in a live incident: n8n source control syncs workflows to a Git repository on licensed setups.12m30xp
4. 4Workflow versioningYou can apply this in a live incident: n8n can keep workflow versions depending on edition and settings.12m30xp
5. 5Execution pruningYou can apply this in a live incident: You configure how long executions are stored and whether success payloads are kept.12m30xp
6. 6Retry on failYou can apply this in a live incident: Retry repeats the node on error.12m30xp
7. 7Manual TriggerYou can apply this in a live incident: Manual Trigger is for on-demand editor runs.12m30xp
8. 8HTML and spreadsheet filesYou can apply this in a live incident: HTML nodes parse markup from a field or binary you point at.12m30xp
9. 9Item linking across nodesYou can apply this in a live incident: Index-based combine assumes aligned lists.12m30xp
10. 10Environment secrets in expressionsYou can apply this in a live incident: $env reads instance environment variables.12m30xp

You can make HTTP behave under real APIs.

1. 1PaginationYou can apply this in a live incident: List APIs page.12m30xp
2. 2Query versus bodyYou can apply this in a live incident: GET parameters belong in the query.12m30xp
3. 3Headers versus credentialsYou can apply this in a live incident: Credentials store secrets outside the workflow JSON.12m30xp
4. 4Content typeYou can apply this in a live incident: Content-Type decides how the body is parsed.12m30xp

You can paginate, auth and respond without duplicating side effects.

1. 1HTTP paginationYou can apply this in a live incident: HTTP Request can follow next-page links when configured.12m30xp
2. 2OAuth callback URLYou can apply this in a live incident: OAuth2 credentials must list the n8n callback URL.12m30xp
3. 3IF conditions and type coercionYou can apply this in a live incident: IF operators depend on types.12m30xp
4. 4Switch fallback outputYou can apply this in a live incident: Switch can send unmatched items to a fallback output.12m30xp
5. 5Wait duration versus cronYou can apply this in a live incident: Wait holds one execution in waiting state.12m30xp
6. 6Execute Workflow TriggerYou can apply this in a live incident: Sub-workflows should start with Execute Workflow Trigger when called as children.12m30xp
7. 7Webhook authenticationYou can apply this in a live incident: Webhook nodes can require a header, JWT or basic auth.12m30xp
8. 8Date and Time nodeYou can apply this in a live incident: DateTime converts timezones and formats.12m30xp
9. 9Spreadsheet File nodeYou can apply this in a live incident: Spreadsheet File reads binary office or csv into items.12m30xp
10. 10Workflow settings concurrencyYou can apply this in a live incident: You can cap concurrent executions per workflow.12m30xp
11. 11Error TriggerYou can apply this in a live incident: Error Trigger is how an error workflow starts.12m30xp
12. 12Renaming json keys for APIsYou can apply this in a live incident: Downstream APIs are name-sensitive.12m30xp