Skip to main content
This walkthrough takes you from a blank canvas to a running workflow using the AI Composer — without dragging a single node yourself. You describe the outcome you want in plain English, the Composer builds it, asks you a few questions along the way, and you run the result and refine it until it does what you need. If you’ve never met the Composer before, the short version is this: it’s an AI agent that reads your request and assembles the workflow for you, edit by edit, right on the canvas.

1. Describe the goal

Write what you want to happen, in your own words. The Composer turns it into a workflow.

2. Refine with questions

The Composer pauses to ask when it needs a choice or a connection. You answer; it keeps building.

3. Run and iterate

Run the workflow, see the result, and send follow-up requests until it’s right.

​
Before you start

You need only a couple of things in place. Everything else, the Composer handles.

An organization you can build in

The Composer is available to organization owners and admins. The previous member role has been retired, so any account that can open the Composer can also use it. See Organizations, roles & membership.

Credits to run on

The Composer runs on managed AI usage, so each turn it takes consumes credits — one credit per turn, plus the cost of the AI model it uses. See Credits & the billing model.
You don’t need any of your integrations connected up front. If a step needs a service you haven’t connected yet, the Composer will pause and walk you through connecting it (see Step 2).

​
Step 1: Describe the goal in plain English

Open a workflow in the builder and switch the right-hand panel to the chat tab — that’s the Composer. A brand-new workflow opens a fresh conversation, ready for your first request. Then write what you want to happen. Describe the outcome, not the steps. You don’t need to know what a “node” is or which pieces go where — that’s the Composer’s job.
1

Write the outcome you want

In the message box, describe the result in your own words. For example: “Summarize new support emails and post a daily digest to Slack.” Press send.
2

Watch it build on the canvas

The Composer plans the workflow, then adds and connects the steps live. New nodes appear on the canvas as it works, and a build-step indicator shows how far along it is. You don’t need to refresh anything.
3

Read its explanation

Alongside the build, the Composer streams a plain-English summary of what it made and why, so you understand the workflow you ended up with.

​
Write a request that gets good results

The clearer your request, the closer the first draft lands. A few habits help:
Say what kicks the workflow off and what it should produce. “When a form is submitted, send the answers to a Google Sheet” gives the Composer both ends to build between.
Concrete details beat vague ones. “Post to the #support channel” is better than “post to Slack.” You can always change specifics later, but giving them up front saves a round-trip.
You don’t have to capture everything in one message. Ask for a first version, look at it, then add to it. The Composer keeps working on the same canvas across the whole conversation.
If you know you want a particular tool — a spreadsheet, a chat app, a CRM — name it. The Composer looks at the integrations your organization has connected and picks the right tools for the job.
The Composer edits the workflow live, but its changes are held as pending changes until you decide what to do with them. Nothing is locked in during this step — you review and confirm later in Step 3.

​
Step 2: Refine with the Composer’s questions

The Composer doesn’t guess on the decisions that matter. When it needs a choice, a piece of text, or access to a service you haven’t connected, it pauses and asks you inline in the chat. This back-and-forth is called human-in-the-loop — it’s how you steer the build without having to touch the canvas yourself. While the Composer is waiting on you, the conversation stays open and nothing else changes until you respond.

A choice between options

The Composer offers a short list and you pick one or several — for example, which model provider a step should use.

A yes or no

A quick confirmation before it does something, such as approving a sensitive action while it test-builds.

Some free text

A short written answer, like the exact wording of a message or the name of a channel.

A connection to a service

If a step needs a service you haven’t connected, the Composer asks you to connect it — and for services that sign in with OAuth, it picks up on its own as soon as you finish.
Most questions are optional. When the Composer can carry on without an answer, it shows a Skip for now action — skip it and the Composer makes a reasonable choice and keeps building.

​
Two rules that keep questions tidy

Only one question can be open per conversation at a time, and only the person who was asked can answer it. If you try to send a new request while a question is still open, the Composer asks you to answer the open one first.

​
Connecting a service mid-build

If a step in your workflow needs a service your organization hasn’t connected yet, the Composer asks for it right when it reaches that step. You connect the service from the question card, and the Composer continues from where it paused. For services that sign in with OAuth — like Google, Slack, or GitHub — connecting opens the provider’s sign-in flow in a new window. As soon as you finish signing in, the Composer resumes on its own: you don’t have to re-send your request or restart the build.
Reconnecting an integration whose access has already expired can’t be refreshed automatically from the app today. If a connection has lapsed, reconnect the integration rather than relying on an in-app refresh. This is a documented gap — see Known limitations.

​
Step 3: Run and iterate

When the Composer finishes a turn, its edits sit on the canvas as pending changes with an action bar. This is your checkpoint: look the workflow over before you commit to it.
1

Review the pending changes

The workflow shows everything the Composer built this turn. Nothing is saved yet — read through the nodes and the Composer’s summary and decide whether it matches what you asked for.
2

Save or revert

Save keeps the changes and updates the workflow’s saved snapshot — this becomes the baseline a later revert returns to. Revert discards this turn’s edits and restores the workflow to its last saved snapshot.
3

Run it

Run the workflow from the builder and watch it execute live. Each step reports as it runs, so you can see what happened and where any output came from. See Running workflows.
4

Refine and run again

If the result isn’t quite right, send the Composer a follow-up request — “filter out spam before summarizing” or “post the digest at 9am instead.” It works on the same canvas, and you run again to check the change.

Save

Confirms the Composer’s edits and refreshes your workflow’s saved snapshot. The new baseline for the next revert.

Revert

Restores the workflow to the snapshot from before this turn and clears the pending changes — a clean undo of the Composer’s latest edits.
Iterating is the whole point. Build a first version, run it, then keep refining with follow-up requests and running again. You only have to save when you’re happy — until then you can revert back to your last good baseline at any time.
Each turn the Composer takes is a fresh run on managed AI usage, so it consumes credits. If your organization is out of credits or over a limit, the turn is refused before any work begins with a billing response — a 402, 403, or 429. See Usage gating & limits and Errors & status codes for what those mean and how to clear them.

​
A worked example

Here’s how the three steps fit together for a common task: turning new leads into a Slack note.
1

Describe it

“When a new lead is added, write a one-line summary of who they are and post it to the #sales Slack channel.”
2

Answer its questions

The Composer asks which Slack workspace to use and prompts you to connect Slack if you haven’t. You connect it from the question card and the Composer continues. It may also ask you to confirm the channel name — you reply #sales.
3

Run and check

You save the pending changes and run the workflow with a sample lead. The Slack note arrives. The summary is a little long, so you send one more request: “make the summary shorter — one sentence max.” The Composer adjusts, you run again, and you’re done.

​
Tips for getting more out of the Composer

The Composer shows each step as it builds. If it’s heading the wrong way, stop the current turn from the chat and start over with a clearer request. Stopping a turn doesn’t undo edits it already made — use Revert for that.
When the Composer edits a workflow you’re co-editing, its changes are shared with everyone in the room automatically, so your teammates see the new nodes appear just as you do. See Canvas collaboration.
The Composer and manual editing share the same canvas. Drag a node yourself, then ask the Composer to extend what you built — or the other way around.
Deleting nodes one at a time is fully supported and syncs to everyone editing with you. A multi-node bulk delete in a single action isn’t handled by the realtime collaboration server today, so delete nodes individually when working with others. See Known limitations.

​
Next steps

AI Composer

The concept behind the Composer, and how it compares to the Assistant.

AI Composer in the builder

The hands-on reference for the Composer panel inside the canvas.

Run your first workflow

Build and run a workflow in the app, with or without the Composer.

Run a workflow from chat

Trigger a workflow you built and watch it run inside a chat.