Skip to main content

​
Describe the job

The Agents page opens with a prompt box. Write the job in a sentence and the agent is written for you: a name, instructions, and the tools it needs from the apps you have already connected.

Describe it

“Summarise my unread emails every morning.” You get a drafted agent to review.

Start from a suggestion

The chips under the box — triage support tickets, research a company, enrich a lead — are the same route with the sentence written.
Drafting needs an AI provider connected and turned on for chat. Without one the page says so and offers to write the agent by hand instead.
Ask for what you want done, not for the tools. The draft only picks an action that reads your data unless the sentence asks for something to be sent, posted or filed, so “tell me when something changes” gets an agent that reports, not one that emails.

​
Start from a blank one

New agent, beside the view toggles on the list, skips the drafting and opens an empty agent for you to write yourself. It goes to your personal project, since an agent you have not deliberately placed belongs to you; where a platform does not create personal projects, the button asks which project to use. Either way you can move it later. A blank agent has no model yet, so it opens straight into its editor with that still to pick.

​
Choose where it lives

Start typing in the prompt box and New agents go to appears beneath it, naming the project the agent will belong to and letting you change it before you create it. That matters because the project is the boundary: an agent reaches only its own project’s connections, flows, tables and knowledge. If you have one project, there is nothing to choose and the control stays out of the way. See managing an agent for moving one later.

​
Set it up

The Configure panel beside the conversation holds everything that changes what the agent does.

Instructions

Write down the job, how to decide, and when to stop.

Agent Tools

Give it the app actions, flows, and MCP servers it needs to reach.

Knowledge Base

Attach the documents and tables it should look things up in.

Model

Pick the model that answers and the key that pays for it.

Output fields

Name the fields you want back, so a flow can use the result.

Max steps

Cap how many actions it can take in one run, so a stuck agent stops.

​
Try it, then put it live

The editor has two tabs beside the Configure panel.

Edit with AI

Describe a change — “only reply to paying customers” — and it rewrites the instructions and tools for you.

Test

Talk to the agent as it is now, and watch which tools it reaches for.
Edits are a draft until you press Publish. The header says which state you are in: Changes not live yet while you are editing, Live once published, and Needs a model to run if no model is picked. Publishing updates every flow already using the agent on its next run, with nothing to republish.
Brief it like a capable new colleague. Say the goal and the edges, not every keystroke. The two people forget most: what “done” looks like, and which calls it should hand back to a human.