Resources / Guides
First workflow guide

Create your first agent.

Start with a ready-made workflow or a JSON export, tailor it in your workspace, give it the access it needs, and validate it before it goes live.

What you will do
Import → edit → test
Open Build → Agent Builder.
Import a cloud workflow or load your JSON file.
Save the imported workflow to My workspaces.
Edit nodes and provide the required access tokens.
Run a test, then publish when the result is right.
01 / Start here

Open Agent Builder.

From the navigation, select Build, then choose Agent Builder. This is where you create, import, and manage workflow drafts in your workspace.

Build navigation with Agent Builder selected
Build → Agent Builder
02 / Import

Bring in a workflow two ways.

On the Workflows page, choose Import from Library. You can select an existing cloud workflow from the library, or choose Load from JSONto import a workflow file supplied by your team.

Workflows page showing Import from Library
Workflows / Import from Library
Import workflow dialog with Import from workflow and Load from JSON options
Choose a cloud workflow or Load from JSON
Imported workflows are added as drafts under My workspaces. Give the draft a clear name before you make your changes.
03 / Customize

Edit the workflow for your business.

Open the draft from your workspace to enter the visual editor. Update the prompts, fields, conditions, and handoffs so every step reflects your process. Changes are auto-saved while the workflow remains a draft.

Workflow editor with connected workflow nodes and components panel
Update nodes in the workspace editor

Use the right components

Add prompts, conditions, messages, and outcome nodes from the Components panel.

Make it autonomous

For an autonomous agent, attach a Dispatcher node after Start. It receives workflow events and routes work into the flow.

04 / Access

Provide only the access the workflow needs.

Open each connected service or action node and add its required access token in the node configuration. Keep tokens in the workspace’s secure credential store—never paste them into prompts, JSON files, or frontend code. Save the configuration before testing.

05 / Validate

Test before you publish.

Select Test in the editor and walk through a realistic input. Check every branch, connected action, and final outcome. When the draft behaves as intended, select Publish to make the workflow available.