Building a workflow

​

Start a new chat

Click New chat in the sidebar to open a fresh session. A chat input and a canvas appear side by side. The canvas is a read-only sketch of what the Planner is assembling — you drive everything through chat, not by dragging nodes.

​

Phrase the intent

Describe what you want done and where the result should land. A single sentence is usually enough:

Every morning, search for the latest AI policy news, summarize the top stories, and email me the digest.

Be specific about the destination — name the Notion database or the email recipient rather than leaving it vague. The more context you give, the better the Planner can pick the right agents and wire them together without extra back-and-forth.

​

Confirm the Requirement Brief

After your first message, the Interview agent produces a Requirement Brief — a short, structured statement of your goal. Review it and confirm. The confirmed brief is what the Planner builds from, so it’s worth a careful read. See Planner for how the two stages fit together.

​

Read the draft canvas

Once you confirm the brief, the canvas populates with a node graph. Each node is one step; edges show execution order — upstream before downstream. Read the graph to confirm the Planner understood your intent before moving on.

​

Answer clarifying questions

The Planner may follow up if something is ambiguous. Answer in chat and be concrete — “the summary goes in the Notes property” rather than “put it somewhere sensible.” Precise answers let the Planner validate bindings without looping back.

​

Handle connection prompts

If a required app isn’t connected yet, the chat surfaces a connection card. Click Connect, complete OAuth in the popup, and return to the chat. The Planner resumes automatically. See Connections for how team-shared connections work.

​

Pick a delivery target

If your workflow writes to a destination like Notion, the Planner asks you to pick the exact database or page. Select a real target — placeholder IDs are rejected at validation and the Planner will ask again. See Approvals for the broader human-in-the-loop pattern.

​

Confirm and deploy

When the plan is ready, the Planner asks “Ready to deploy?”. Confirm in chat and the workflow is created and queued. If you refine and redeploy within the same session, the existing workflow is upgraded in place — no duplicate is created. See Workflows for lifecycle details.

​

Make it run on its own

A deployed workflow runs on demand by default. To run it on a schedule, from a webhook, or via the API, attach a trigger.