Building automations
You can write an automation and save it switched off. You cannot switch it on: a person does that in the app after reviewing it, because once on it runs on real records.
- Find the building blocks:
workflowswith actionstepsand a search for what you want to do (send a message, change a record, check a condition). Connected apps show up here too. - Read what each one needs:
workflowswith actionstep_detailsfor up to 10 steps at once. Use the exact field names it gives. Look up the workspace's own tables and fields first withdescribe_workspace_schema. - Write the whole definition: a name, a displayName, a trigger, a start step and the steps. Every step needs a short label and description in plain words.
- Check it:
workflowswith actionvalidate. It lists every problem with the step and field. Fix them and check again until it is clean. - Save it:
manage_workflowswith actionsave_draft. A definition with problems is refused and nothing is saved. - Confirm it exists:
workflowswith actionsavedlists every saved automation and whether it is on. The one you saved shows as off.
Rules
- Say it plainly: the automation is saved but not on, and the person turns it on in the app (Autopilot) after checking it.
- Never say it is saved until
save_drafthas succeeded andsavedshows it. - Ask when a choice changes what the automation does (who gets told, which stage, how many days). Pick a sensible default for the rest and say which you picked.
- You cannot edit or delete a saved automation from here. To change one, save a corrected new draft.


