• Triggers: how workflows start

  Every workflow starts with a trigger. The trigger determines *when* the workflow runs and *what data* it starts with. This article covers the seven trigger types, when to pick which, and the configuration that matters for each.Few readers

• 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.Few readers

• Error handling and retries

  Workflows that process real-world data will fail. Files get corrupted, APIs go down, AI models refuse, networks hiccup. The difference between a workflow you trust and one you don't is how it handles failure. This article covers the three error-handling patterns and when to use each.Few readers

• Node deep dive: Data Extractor

  The **Data Extractor** is the most-used node in Lido workflows. It takes a file or email and returns structured data using the same engine that powers the spreadsheet UI.Few readers

• Node deep dive: AI Agent

  The **AI Agent** node lets you run an LLM call inside a workflow. Use it for transforming, classifying, summarizing, or generating content at any step. Where the **Data Extractor** is purpose-built for "document → structured data," the AI Agent is general-purpose.Few readers