Business· Help center

Help center › Automations

How to have Otto build an automation for a client

For agencies. Client projects → Client automations → Build with Otto. Describe what the client needs, pick what to deliver, and Otto's coding agent builds it in a sandbox with sample data. It uses part of the month's AI allowance, and it is off until switched on for your server.

Updated 2026-10-27

If you build automations for clients, Otto can build one for you. You describe what the client needs in plain words, name the apps involved and pick what to deliver. Otto's coding agent builds it, tests it on sample data and hands back the files, with a setup guide for your team and a short note for the client.

Building with Otto is off until it is switched on for your server. While it is off, the Build with Otto button is greyed out and says why beside it.

Where

Open Work → Jobs, switch to the Client projects view and press Client automations. Build with Otto is at the top, with the list of builds and how each is going. Each automation in the register also has its own Build with Otto button, which starts the form from that automation. Only people whose position sees all the work see builds, and only someone who manages the business starts, changes or continues one.

What Otto can deliver

  • An n8n workflow to import: a workflow file your team imports into n8n.
  • A Make scenario blueprint to import: a blueprint file your team imports into Make.
  • A step-by-step Zapier setup guide: Zapier cannot import a file, so this is a guide that names every step and every field to fill.
  • A small Node or Python service, with tests: the code, its tests and how to run them.
  • An Otto AI tool to publish: a tool definition. Add to AI tools adds it to your AI tools tab, unpublished, when AI tools is switched on.

Every build also comes with a README (numbered setup steps and the accounts to connect), a handoff note for the client in plain words, and the sample data it was tested on with the result of that test.

Steps

  1. Press Build with Otto.
  2. Pick a common build to start from if one fits, such as New order to a Notion database, Form lead to CRM and a Slack alert or Invoice reminders. It fills the form, and you can change anything.
  3. Pick the client, give it a name and say What should it do? in a sentence or two.
  4. Add the Apps involved, by name only.
  5. Choose What to deliver.
  6. If the client sent you an email or a process note, paste it under Material from the client. Otto treats it as information about the job, never as instructions.
  7. Check what it will use, shown beside the Build button, and press Build.

The build shows what the agent is doing as it works. When it is done, its files are listed with Download buttons and the README is shown on the page.

Real accounts are connected by you

Otto never asks for, and never keeps, a password, an API key or a login for a client's systems. The agent builds and tests with made-up sample data in a sandbox that cannot reach the client's accounts. Your team connects the client's real accounts when importing what was built. A field with something that looks like a password, a key or a login in it is refused.

What it uses

A build is AI work, so it uses part of this month's AI allowance, like everything else Otto does. Before you press Build, the form says the most it may use, as a share of the month's allowance: the most one build may use, or what is left this month if that is less. What builds used is included in Settings → Usage.

  • If it reaches that amount before it is done, it pauses as Paused at its budget. Continue gives it another share.
  • If the month's AI usage is spent, a build cannot start. It starts again next month, or a manager can set an extra-usage budget in Settings → Usage.

Change it

Under Change it, say what to change and press Send the change. Otto picks up the same build where it left off, or starts a fresh one from the last version's files. A change uses another share of the allowance.

Add it to the client's automations

Add to the client's automations adds the build to the register with its name, what it does and the apps it uses, as Building. Pressed again, it updates the same automation. Set it to Live once your team has connected the client's accounts and it runs.