Help Centre › Building Processes
Autopilot builds a process for you. You describe a task in one or two sentences, the bot works it out on the screen of the machine it runs on, and the steps it took are saved as a normal process that you can edit, schedule and share.
1. What Autopilot needs
Open Autopilot from the menu. The page says either "Autopilot is ready to use on this company." or "Autopilot is not ready yet.", and lists three checks under What Autopilot needs. Each one that is missing has a button to fix it.
| Check | How to fix it |
|---|---|
| Autopilot is included in your plan | Autopilot is on plans that include Autopilot (record from a prompt). Click See the plans. |
| Autopilot is switched on for this company | It is off until a company admin switches it on under Settings › Functionality. |
| Your own AI account is connected | Add an Anthropic or OpenAI connection with your own API key under Connectors (Add an AI connection). |
2. Whose AI account pays
Autopilot always runs on your own AI account, never on ours. It uses a lot more AI than anything else on the platform, so there is no fall-back to Automize's account. If no Anthropic or OpenAI connection is saved, the bot stops and shows the reason.
- If you have both, it uses the AI provider your company prefers.
- Azure OpenAI is not supported for Autopilot yet.
- Your provider bills you for what Autopilot uses. Set a spending limit with your provider if you want one.
See Working with connectors for how to add a connection.
3. Start one
- Open the Automize bot on the machine where the work happens. The bot must be connected (see Connect a bot to your workspace).
- On the Processes panel, open the Record menu and choose Record from a prompt…
- Under What should the bot do?, describe the task. Say which items it repeats over, which site or app to use, what to capture, and where the results should go.
- If you have a working instruction or process map that already describes the task, choose it under Working instruction or process map (optional). The bot reads it as well as your sentence.
- Type a name under Save the recorded process as: and start.
A small progress window shows what the bot is doing. While Autopilot runs, the bot counts as busy and does not start other runs.
4. You approve anything risky
Before a step that could change or send something, such as clicking Pay or Submit, the bot stops and asks "The bot wants to: … Allow it?"
- Click Yes to let it go ahead, or No to refuse.
- If nobody answers within 5 minutes, the answer is No. Stay near the machine while it records.
5. Repeated steps become a loop
If the bot did the same steps for several items, it offers to save them as one loop instead of a long list of repeated steps ("Save it as a loop?"). Say yes for a process that is easier to read and works for any number of items. If you say no, or the loop cannot be built, it saves the steps as recorded.
6. After it finishes
The process is saved in your workspace like any other. Open it, check each step, and test it before you rely on it. Autopilot gets you a first draft quickly; it does not guarantee the draft is right. See Running and debugging a process.
7. If it will not start
| Message on the bot | What to do |
|---|---|
| Autopilot is not included in your plan. | Ask your administrator to change plan. |
| Autopilot is switched off for this company. | Ask a company admin to switch it on under Settings › Functionality. |
| Autopilot runs on your own AI account. | Add an Anthropic or OpenAI connection under Connectors, then try again. |
The Autopilot page in the browser always shows which of the three checks is missing.