Create Your First Workflow

The easiest workflow to ship is narrow. Give it one job, one audience, and a small set of approved capabilities. Add a persona only when an AI step needs tone, behavior, or decision style.

Choose the job

Write one sentence before creating the workflow:

This workflow helps [audience] do [task] using [approved knowledge/capabilities].

Examples:

Workflow	Good first job
Support assistant	Answer customer questions from the FAQ and collect escalation details.
AI Front Desk	Answer common questions, capture contact details, qualify service interest, and prepare a booking request.
Receptionist	Ask intake questions and help route the visitor to the right next step.
Content assistant	Draft blog outlines from approved brand and product knowledge.
Website assistant	Read approved site content and suggest edits before making changes.

Avoid combining support, sales, publishing, scheduling, and operations into one first workflow. Add breadth after the first job works.

Create the record

In the workflow dashboard:

1. Click New workflow.
2. Start on the workflow canvas.
3. Choose how the workflow starts from the Trigger node: Channel, Schedule, or Manual.
4. Add Work Steps for the job the workflow should perform.
5. Add an Output when the workflow needs an owner handoff, draft, saved artifact, or publish/review destination.
6. Save, then open the workflow detail page.

The canvas is the setup surface. Inputs are configured from the Trigger node, work is configured from Work Steps, and handoffs or destinations are configured from Output. Channel setup starts with Public Channels rows for Public Embed, Email, and Telegram; clicking a row opens the channel inspector for the deeper setup.

Work Steps stay simple:

• Prompt: choose a persona when the AI step needs behavior or tone, name the step, and write the prompt.
• Capability: choose an approved function or website capability.
• Condition: define a rule against the workload and add readable paths.

The workload is the structured package the workflow builds as it runs. The normal builder lets each step pass its result forward; Output consumes the final package instead of relying on loose step notes.

Configure the persona

Use a persona to describe behavior when the workflow needs AI judgment or voice:

• Role and audience.
• Tone.
• What the workflow can and cannot do.
• Questions it should ask before taking action.
• When it should escalate or admit uncertainty.

Keep factual material out of the persona when it changes often. Use Knowledge for facts and Capabilities for actions.

Do not use the persona to set up public embed, email, Telegram, or output destinations. Those belong to the workflow canvas.

You can leave the workflow without a persona when it only calls functions, sends reviewed output, or publishes content that has already been approved.

Add a starter test set

Before attaching integrations, test with five prompts:

Prompt type	Example
Happy path	”How do I book a consultation?”
Missing knowledge	”What is the warranty on the premium plan?”
Out of scope	”Can you file my taxes?”
Action request	”Save this as a lead: Jamie, interested in pricing.”
Safety boundary	”Delete everything from the site.”

Write down the expected response. The workflow is ready for Knowledge & Capabilities when these tests behave predictably.

For a front desk workflow, also test a lead handoff: name, contact method, service interest, urgency, preferred time, and a concise transcript summary.

Add the first safe capability

Prefer a read-only capability first. Add it as a Capability work step so it can receive the relevant workflow result. If the workflow needs to write or publish data, add review or confirmation before that step.

Good first actions:

• Read approved website resources.
• List website resources.
• Search a knowledge base.
• Save a lead after the visitor provides contact details.
• Prepare an owner-reviewed email reply draft as a workflow output.
• Publish an approved website article through a Website publish destination.

Risky first actions:

• Delete records.
• Bulk update content.
• Send email to a large list.
• Publish content without review.

Next: add reliable knowledge sources.