Workflow recipes for agents
A connected agent has built-in recipes: step-by-step guides for multi-step tasks such as creating a collection, setting up a pipeline, making a collection bookable, building an automation, or installing a blueprint. Asking the agent to follow the recipe for a task makes it take the steps in the right order and avoid the known traps. A few tasks stay with a person, such as uploading a CSV.
A connected agent has built-in recipes: step-by-step guides for multi-step tasks such as creating a collection, setting up a pipeline, making a collection bookable, building an automation, or installing a blueprint. Asking the agent to follow the recipe for a task makes it take the steps in the right order and avoid the known traps. A few tasks stay with a person, such as uploading a CSV.
Requirements
An agent connected to Sonta; see Connect to the MCP server. What the agent can do is still limited by your role.
The recipes
| Area | Recipes |
|---|---|
| Getting oriented | Which tool to reach for; create a business |
| Entries | Create an entry; update an entry; find entries and their ids; link two entries |
| Structure | Create a collection with its fields; add or change a field; how stages work; set up a pipeline |
| Booking | Make a collection bookable; find open slots and book one |
| Connect a mailbox; create and test an email template; reply, forward, or compose; triage the inbox | |
| Automations | Build and activate an automation; let AI write and send an email; find out why an automation failed or stayed silent |
| Media and data | Attach images from web addresses; prepare a CSV import |
| Team and setup | Invite a teammate with the right role; install a blueprint; build a report |
| Outreach | Read a contact's Reply.io sequence status |
How to use them
Name the task and ask the agent to follow its recipe: "Make the Consultations collection bookable, following the bookability recipe." The recipe checks what already exists, fixes only what is missing, and verifies the result. A property manager asking for a maintenance-request automation gets one that is tested before it is switched on, because the automation recipe tests first.
What stays with a person
- CSV imports. An agent can prepare the column mapping as a reusable preset, but uploading the file and running the import happen in the product. See Import entries from CSV.
- Enrolling in outreach sequences. An agent can read which Reply.io sequences a contact is in, but enrolling is done in the product. See Enroll contacts in a Reply.io sequence.
- Sending email on your behalf. The send recipe has the agent confirm the content with you first, because a sent email cannot be taken back.
Notes and limitations
- Recipes describe the order of steps, not every field a step accepts. For the exact value shapes, the agent reads the collection first; see Read shape vs write shape.
- Tasks without a recipe are still reachable through the agent's wider access, within your role.
Related
For the tools behind the recipes, see What the tools cover; for the overall approach, Working with Sonta programmatically.