Skip to main content
Use this reference to pick the right node for each step of your automation. Grouping mirrors the builder palette. Each entry highlights when to use it, key parameters, and outputs.

​
System

  • Start (START) — required entry; one per flow. No params or outputs.
  • End (END) — terminates the run. Add error transitions on upstream nodes for resilience.

​
Browser automation & AI

  • Agent Action (AGENT_ACTION) — general-purpose AI agent that can browse websites, process data, call integrations, search the web, and more. Handles all browser interactions (navigation, clicking, typing, scrolling, data extraction) through natural language prompts. See Agent Action for full details. Attach Skills for reusable guidance.
  • Login (LOGIN) — apply stored credentials at the right moment; keeps secrets out of nodes.

​
Data capture & transform

  • Process Data (PROCESS_DATA) — prompt-based transform. Declare outputs (name, description, type: scalar | list | object | object_list); ${var} tokens interpolated. Add schema fields for object/object_list so downstream steps and API callers see the shape.
  • Parse Document (PARSE_DOCUMENT) — parse a file URL or canonical variable; emits ${node_id}.parsed_result_json and ${node_id}.parsed_result_url.
  • File Output (FILE_OUTPUT) — write text/JSON to storage; exposes path at output_variable_name.

​
Communication

  • Send Email (EMAIL_SEND) — send via Resend; to, subject, and html_body accept ${variable} interpolation. Optional params: reply_to (Reply-To address), in_reply_to (Message-ID for threading), and attachments (list of file URLs with optional filenames).

​
APIs & integrations

  • API Request (API) — call any HTTP endpoint (GET/POST/PUT/PATCH/DELETE) from within a task. Provide URL, optional Bearer token, JSON body with ${variable} interpolation. Params: timeout_ms (default 30 000 ms) and output_variable_name (default response). The JSON response is parsed and stored at ${node_id.output_variable_name} for downstream use. Use the in-builder Send test button to try sample requests safely.

​
Composition

  • Task (TASK) — embed another published task as a child step. Maps parent inputs to child, lets you choose child outputs to surface, and runs the latest published version by default (auto-updates). Switch to “Pin to version” when you need a fixed child definition.

​
Logic & control

  • If / Else (IF_ELSE) — branch on plain-language condition; routes to true/false handles.
  • Loop (LOOP) — iterate over a canonical list variable (no ${}); inside the loop use ${loop_id}.current_item and ${loop_id}.current_item_index.

​
Tips for reliable runs

  • Use Agent Action for all browser interactions. Describe what you want in natural language and the AI agent handles navigation, waiting, clicking, typing, and extraction.
  • For downloads, use Agent Action to click download controls. Prefer absolute URLs; use Process Data to prepend host/scheme to relative links.
  • Keep node descriptions short and action-oriented so collaborators quickly understand intent.
  • For AI-driven actions (Agent Action, Login), add Visual references in Advanced options so the agent sees what “success” looks like. Use tight, well-labeled screenshots for best results.