Nodes reference (overview)

Workflow nodes are organized into seven categories. This article is the map: it lists every node, says what it does in one line, and points to the right specialized article when you need depth. Use it as the index when you're building a workflow and trying to find the right node.

For full parameter reference on any node, see the Lido docs at docs.lido.app/Workflows/Nodes/.

Triggers

Trigger nodes start workflow execution. Every automated workflow needs at least one trigger. See Triggers: how workflows start for full coverage.

Data Operations

Read from and write to your data sources.

The Data Extractor is the most-used node in this category. See Extract data from PDFs and documents and Automate extraction with workflows.

Transformations

Modify and reshape data flowing through the workflow.

Edit Item is the workhorse here. Use it to attach metadata (timestamps, source filenames, computed fields) to items as they flow through the workflow.

JS Code is the escape hatch when no other node does what you need. Use it sparingly — every line of JS is something to maintain.

Flow Control

Route data through different paths based on conditions.

Use If for binary decisions, Filter for keep/drop, Switch when you have 3+ branches.

Error Catcher is one approach to error handling; the other is connecting individual nodes' error outputs. See Error handling and retries.

External Services

Talk to APIs and services outside Lido.

API Request is the catch-all for any external system that has an HTTP API. Use it to push to your CRM, your database, your in-house tools.

File Operations

Manipulate files: format conversion, copying, OCR, splitting, combining.

OCR PDF before Data Extractor is a critical pattern for scanned documents. See Improve extraction accuracy.

Templates & Forms

Generate documents from templates and fill PDF forms.

Use these to generate filled-in versions of your standard forms — invoices, contracts, applications.

Common features across all nodes

Parameters vs. Settings

Every node has two configuration sections.

• Parameters — what the node does. Field mappings, expressions, source/destination, etc.
• Settings — how the node executes. Batch size, error handling, retries, concurrency.

Beginners often miss Settings. The controls there matter for reliability and cost on production workflows.

Error output

Every node has a success output (right side, default flow) and an error output (separate). When an item causes an error:

1. An error item is created with the error message attached.
2. The error item flows out the error output (if you've connected it).
3. Other items keep processing — unless stop on error is enabled in Settings.

Wire up error outputs in production workflows. Silent failures are much harder to debug than loud ones.

Expressions

Most parameters support {{...}} expression syntax to reference upstream item data, dates, and more. See Expressions and the formula bar.

{{$item.data.fieldName}}
{{$today().plus(7, "day")}}
{{$("Get Table").item.data.recordId}}

Tips

• Search by category, not name. When you need a node, think about what it does (transform? send? trigger?) and look in that category first.
• Use Edit Item liberally. It's free debugging context — attach the timestamp, source file, run ID to every item early in the workflow.
• Reach for JS Code last. Most things you'd write in JavaScript already have a dedicated node.
• Document Classifier + Switch + Data Extractor is one of the most powerful patterns in Lido. Use it whenever you have mixed inbound document types.
• API Request handles auth headers, query params, and file uploads. Don't drop to JS Code for HTTP — API Request can do it.

Related articles

• Build your first workflow
• Triggers: how workflows start
• Error handling and retries
• Expressions and the formula bar
• Extract data from PDFs and documents
• Automate extraction with workflows
• AI columns and formulas

Updated on: 16/04/2026