Overview

A workflow connects several assistants under one coordinating node, called a supervisor, so a single question can be answered by the assistant best suited to it, or by several assistants together. You build a workflow on a visual canvas, then chat with it the same way you chat with an assistant.

Why workflows matter

One place to ask. People don't need to know which assistant covers which topic. They ask the workflow, and the supervisor decides which assistants handle the question.

Specialized assistants stay focused. Each assistant keeps its own instructions and knowledge. The workflow combines them without merging them into one large assistant.

Broader answers. For questions that span several areas, the supervisor can combine what several assistants say into one answer.

How workflows work

You create a workflow in a project, give it a name, and open it on the canvas.

You add one supervisor and choose its type: Router, Consolidator, or Planner.

You add at least two assistants from the same project and connect each one to the supervisor.

You publish the workflow. It then appears in the Workflows list with the status Live, and people with access can chat with it.

When someone asks a question, the supervisor sends it to the connected assistants according to its type and returns the answer. In the chat, Thought Process opens an Activity panel that shows the steps the supervisor took, such as which assistant a Router sent the question to.

A workflow on the canvas: a Router supervisor connected to two assistants

Key terms

Workflow: A set of assistants connected to one supervisor on a canvas. A workflow belongs to one project.

Supervisor: The coordinating node that plans, routes, and oversees how a question is handled across the connected assistants. Every workflow has exactly one.

Assistant node: A place on the canvas for one assistant. Each node uses a different published assistant from the workflow's project.

Canvas: The visual editor where you add the supervisor and assistants and draw the connections between them. It always starts with Start, Input, and End nodes, which mark where a question enters the workflow and where the answer leaves it.

Model: The default AI model the supervisor uses to coordinate the connected assistants.

Supervisor types

The supervisor type decides how a question moves through the workflow. You choose it when you add the supervisor, and you can switch it from the supervisor's Type setting on the canvas.

Type	What it does	Best for
Router	Picks the most relevant assistant's response for the question and validates it, so the best single answer is shown.	Questions that one specialist can answer, when you want the best match rather than a combined answer.
Consolidator	Collects responses from all connected assistants and combines them into one answer, weighting each by how relevant it is to the question.	Questions that touch several areas, when you want every assistant's view in one answer.
Planner	Breaks the question into parts and engages the assistants needed for each part.	Multi-part requests, where different assistants handle different pieces of the task.

Use cases

Employee help desk: Connect an HR assistant, an IT assistant, and a finance assistant to a Router. Employees ask one workflow about leave, laptops, or expenses, and each question reaches the assistant that knows the answer.

Research summaries: Connect assistants that each cover a different market or product line to a Consolidator. A question like "What changed this quarter?" returns one answer that brings together what each assistant knows.

Multi-step requests: Connect a policy assistant and a travel assistant to a Planner. A request like "Plan a client visit to Berlin within policy" is split into parts, and each part goes to the assistant that handles it.

If one assistant already covers everything your users ask, you don't need a workflow. Share that assistant directly instead.

Who can access workflows

What a person can do with a workflow comes from their Permission Sets, together with their role on the workflow (Owner, Admin, or Member) or access inherited from its project or team. Workflows can't be made public. To learn how this works, see Workflow Access Control.

Guides

Add Workflow: build a workflow on the canvas and publish it.

Workflow Chat: ask a workflow questions.

Workflow Edit Access: give users and teams access to a workflow.

Why workflows matter#

How workflows work#

Key terms#

Supervisor types#

Use cases#

Who can access workflows#