Concepts

Tasks

The building blocks of a workflow — every step in the graph is a task.

A task is a single step in a workflow. Each task type has a defined set of inputs, configuration options, and outputs. The auto-generated Task reference lists every task type with full schemas; this page covers the categories and the cross-cutting behavior.

Task categories

  • Data — Find Prospects, Enrich, Update Record, Get Record.
  • AI — AI Prompt (Text / Object / Image), Research Signal, Agent (invoke an agent as a step).
  • Control flow — Nested Workflow, For Each, Conditional.
  • Integrations — Instantly Sequence (add contacts to an Instantly campaign), Sanity (publish documents), and others. Integration tasks resolve credentials per-organization from the corresponding integration settings, with environment fallbacks for local/system workflows.

Adding a task

In the workflow builder, Add a task opens a two-pane picker:

  • Categories on the left, click-to-lock (cursor doesn't change the visible task list as you move it across the sidebar).
  • Tasks on the right, with a top search that flattens results across categories.

Brand-styled at 720×480 with a gradient header and a clear search/category state.

Cross-cutting behavior

A few patterns show up across task types:

  • Variables in / variables out — every task declares its inputs and outputs. Outputs become available as {{steps.N.<output_name>}} to downstream tasks. See Variables.
  • Array outputs — tasks that produce arrays (e.g. Find Prospects' prospects and contact_ids) are tagged in the variable picker with a purple arr badge so the For Each task's Items Array picker shows them clearly.
  • Type coercion — Update Record accepts comma-delimited strings (e.g. "vip, customer") and JSON arrays for text[] fields like tags, so users don't get "expected an array, received a string" errors.
  • Default models for AI tasks — Field tasks resolve their default model from the ai_models.is_default_field_task_model flag, with gemini-3-flash as the last-resort fallback. Admins can change the default and bulk-migrate existing tasks at /automation/workflows/fields.

See also

On this page