Skip to content

Web App Controls

Where is the control you need? Use Home for the in-product builder, Agents for agent editing and conversations, and Workflows for flow canvases. The main navigation has no top-level Build tab. Builder chats belong under Home.

Destination App route What to open
Home / Enter a request and choose Build for me.
Agents /agents An agent’s editing or conversation screen.
Workflows /workflows An existing workflow, New workflow, or Templates.
Connections /connections Your connected app accounts.
Settings /settings Account, Organization, Subscription plan, API keys, AI assistants (assistant setup and connected assistants), and Coding subscriptions.

Use Connect Your Apps for provider accounts, Manage Account Usage for billing, and Assistant Access and Security for credentials.

With an assistant: call workflow_list, called with { "limit": 100 }, owned agents with agent_list called with {}, shared agents with agent_list called with { "ownership": "shared" }, and connections with connection_list called with {}. Every workflow-scoped tool call carries an explicit workflowId.

Note the workflow’s data.items[].id as <workflowId> and check data.hasMore. workflow_list defaults to 25 workflows and caps limit at 100. It provides no next-page cursor. If the target is absent with hasMore: true, use Workflows search and read its ID from the URL. The app’s All agents includes owned and shared agents. agent_list defaults to owned agents.

Not every assistant capability has an app control. The account feed uses event_list, and there is no main-menu Activity screen. Pass workflowId to filter it to one workflow, or omit it for account-wide events. See Review Account Activity.

Open an agent and use its mode switch.

Mode What it uses Next action
Edit The draft configuration. Change instructions, tools, or reference files, then Save.
Test Draft conversations. Send representative requests and inspect the result.
Live The published version. Use published conversations; Live is unavailable before publication.

In the files panel, Reference means knowledge files, Runtime means the shared runtime workspace, and Conversation needs a selected conversation. Runtime lists development files in Test and live files in Live. A Test conversation sees live runtime files plus development files. When both hold the same path, the development copy wins. See Manage Agent Files, Test Your Agent, and Publish and Share Agents.

Where are a workflow’s inputs and results?

Section titled “Where are a workflow’s inputs and results?”

Open Invoice intake, choose Dev, then select Check invoice in the flow list. The development version and live release have separate views.

Need Control What to inspect
Accept values Selected flow → Inputs → Add new input, or a row’s Edit Display name, type, description, and Required.
Define returned values Selected flow → Outputs → Add new output, or Edit Display name, type, and description.
Configure start events Selected flow → Triggers → Add new trigger Trigger sources and mappings.
Choose expression data Focus a field → Insert dynamic data; in a block, click Dynamic data or an existing token Search available inputs and operations; see Use Expressions.
Read stored records Data tables Workflow data collections for the selected version.
Inspect saved definitions Version history Saved changes and available restore controls.
Run the selected flow Header Test Tooltip: Test current flow.
Run one supported node Node menu → Test action That node’s configuration.
Inspect an execution Header Run history Node Inputs, Process, and Outputs.

For Check invoice, inspect Invoice ID and Amount under Inputs, and invoice_id and review_needed under Outputs. These are the running example’s contracts. Use Define Flow Contracts to change them.

When a flow needs inputs or runtime context, Test opens a values panel. Otherwise it can start immediately. Development tests can perform real provider actions and consume usage. Follow Test a Workflow and Debug a Run for app and assistant verification.

  1. Open Workflows → Templates.
  2. Choose Use template on the template you want.
  3. If Connect accounts opens, select your connections and choose Copy workflow. Skip for now copies without those account mappings.
  4. Inspect the copy that opens in your account. Saved flow test values and data records are not copied. Enter your own values, and populate any required Data tables, before testing development flows.

The copy is inactive, with a development definition and no published release. Copying can create real trigger sources and capture events before publication, separately from live workflow execution. Setup errors for email, webhook, and schedule sources are caught, so the copy can succeed with no source attached. Confirm that every copied trigger has a source, and check each action’s destination, before you test or publish. See Start with Triggers.

With an assistant: read the copy’s <workflowId> from /workflows/<workflowId>/versions/<workflowVersionId> in its URL, then inspect it with workflow_get and flow_list, each called with:

{ "workflowId": "<workflowId>" }

In editable Dev, the bottom toolbar offers Hand tool, Move, Undo, and Redo. Live omits Undo and Redo.

Interaction Result
Hand tool Drag the canvas to pan; use the wheel to zoom.
Move Wheel to pan; drag a selection rectangle that includes partially overlapped nodes.
Hold Shift Select multiple elements.
Hold Space Temporarily enable panning.
Pinch or double-click Zoom when the canvas is unlocked.
Bottom-left controls Zoom in, Zoom out, Fit view, Auto layout, and Lock/Unlock canvas.

Zoom ranges from 10% to 120%. Lock blocks node dragging, new selection, wheel/pinch/double-click zoom, and the zoom, fit, and layout buttons. It still permits connecting nodes and deleting already-selected elements.

Shortcut Action
Cmd+Z on Mac; Ctrl+Z elsewhere Undo.
Cmd/Ctrl+Shift+Z Redo.
Cmd+Y on Mac; Ctrl+Y elsewhere Also redo.
Delete or Backspace Delete selected nodes first, or selected edges if no nodes are selected; trigger selection opens a deletion dialog.
Cmd/Ctrl+backslash Collapse or expand the flow panel.

Undo, redo, and delete shortcuts do not run while typing in an input, textarea, or editable content, or while the workflow is read-only. The flow-panel shortcut also ignores select fields and dialogs opened from that panel.

Undo and Redo cover locally recorded definition edits and flow/trigger navigation, with up to 100 entries. Undo can open the previous canvas instead of reverting an edit. History starts empty in a new builder session. Remote edits add no Undo entry, but an edit arriving after Undo discards Redo.

Node dragging adds no Undo entry and does not itself trigger a save. Bottom-toolbar Auto layout also skips Undo and only changes the current view. Reloading restores persisted positions unless another definition save captured the changes.

Undo is not record rollback, and it cannot retract a provider action. For saved definitions, use Version history and Restore Earlier Changes. Restore depends on access and state availability, and does not restore record values.