Node reference

Nodes are the building blocks of EzFlow workflows. Each node performs one well-defined action — sending a message, calling an API, evaluating a condition, transforming data, and so on. You connect nodes on the canvas to define the exact sequence of operations your workflow executes. This section is the per-node reference: one page per node type, documenting its purpose, I/O handles, and configuration fields.

Node categories

• Triggers — start a workflow run (HTTP, cron, form submissions, webhooks, Slack, and calendar events)
• Messaging — send email, SMS, WhatsApp, and Slack messages; fill templates
• LLM / AI — call large language models with your own API key
• HTTP & Integration — make outbound HTTP requests and call third-party integrations
• Logic — branch, combine, and filter with conditions and boolean operators
• Data transform — convert, map, merge, decompose, and script data
• Files & PDF — upload files, retrieve storage objects, and generate PDF documents
• Database — search, create, update, and remove records in EzFlow databases
• Marketing — manage contacts, lists, segments, suppression, and activity logs
• Pipeline (Kanban) — create, move, update, and delete cards on Kanban boards
• Calendar — list, create, update, cancel events and check availability
• Slack — listen for Slack events and send approval requests
• Flow control — pause execution, wait for user responses, and branch chatflows

How to read a node page

Each node page has four sections:

• What it does — a plain-language description of the node's purpose.
• Inputs & outputs — the handles available on the node's left (input) and right (output) edges. Connect these to pass data between nodes.
• Configuration — the fields you fill in on the node's config panel, with their types and whether they are required.
• Example — a real-world usage example showing inputs, configuration, and expected outputs.