Tasks

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, Get Record, Create Record, Update 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), LinkedIn Action (send connection requests/messages or create posts through a connected LinkedIn account), 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, account_ids, 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.
• Record resolution — Get Record can look up accounts and contacts by stable identifiers such as domain, email, CRM id, or LinkedIn URL, and can create the record when missing. Use that pattern before Create Record when logging an activity that should attach to the right contact/account.
• Default models for AI tasks — New agents, AI Prompt tasks, Research tasks, Research Signal scoring, Field tasks, image generation, and Genie query building resolve defaults from the admin model catalog's Default Usage settings. Existing saved workflows, agents, and field tasks keep their stored model until an admin or automation user migrates them.
• Side-effect tasks — tasks that send email, Slack, LinkedIn messages/connection requests, or publish content run for real when a workflow runs. Use connected test accounts and stable idempotency inputs before enabling them in production automations.

See also

• Task reference — auto-generated reference for every task type.
• Variables — how data flows between tasks.