Workflow
A declarative spec, a versioned JSON document, that describes a multi-step automation: the steps, what each does, which tools it can use, which assertions must pass, and where to branch. Workflows are reusable, schedulable, parameterizable, shareable and compiler-validated. They’re the primary unit of authored IP. See Build a workflow in chat.
Step
One typed node in the workflow graph. There are ten step types; agentic steps compile into small agents with only what that step needs, and deterministic steps run without a model. See Step types.
A callable function with a declared JSON input schema and return type. Tools are the leaf operations. See Custom tools.
Skill
A reusable bundle of instructions, templates and checks for one capability. A tool is a function call; a skill is a packaged way of solving a class of problems. See Custom skills.
Subagent
A specialized agent that a coordinator hands a substantial sub-task to, such as schema analysis, research or root-cause investigation. The coordinator resumes when the subagent returns. It keeps the top-level interaction readable. A subagent is different from a subworkflow, which calls a saved workflow by ID.
Trigger
A persistent, project-scoped record that starts one to ten workflows: on a cron schedule or from a webhook. A manual click or a run from chat is a run mode, not a trigger. See Trigger reference.
Action step
A step that changes something in the world, with a plan, freeze, optional approval, execute and audit lifecycle. See Actions and approvals.
Project
The customer-facing container that scopes conversations, metrics, workflows, tools, skills, triggers, connectors and settings. See Create a project.
Semantic layer
A shared, versioned description of selected data and its business context. Projects pin an exact built version. See Create a semantic layer.
Metric
A project-scoped, versioned SQL definition, validated against the project’s data. See Create a reusable metric.
Response contract
An optional shape that chat’s final answer must follow. See Structure chat answers.
Artifact
A durable output, such as a data file, chart, image or report, stored outside the message stream and referenced from a conversation or run. FileRef, S3PathRef and ArtifactRef move large results between steps without copying them into every model context. Last modified on October 1, 2026
