Connect a bot to your workspace

Each machine that runs the Automize bot has its own key. You connect it once with a short code that someone approves in the browser. No person's password is kept on the machine.

1. Install the bot

1. On the dashboard, choose Download bot.
2. Run the installer on the machine that will run your processes. The bot runs on Windows, macOS and Linux.
3. Start the bot. The first time, it shows the Connect this bot screen.

2. Connect it

1. On the bot, choose Connect this bot. The bot shows an 8-character code, such as K7PM-3XQD, and opens a page in your browser.
2. Sign in to Automize in that browser if you are not already signed in.
3. Check that the machine name and the code on the page match what the bot shows, then click Approve.
4. Go back to the bot. It connects by itself within a few seconds.

If the browser did not open, go to /connect on the Automize website from any device, sign in, and type the code.

The code lasts 15 minutes. If it runs out, choose Start again on the bot.

3. Whose access the bot runs with

A bot runs for the person who approved it. It reads and writes data with that person's access, in the workspace the browser was in when they clicked Approve. Its actions are recorded as that person, and the security log records which machine got a key, from whom, and when.

• A company admin can change this with Runs for on the bot's page, for example when someone leaves.
• If the person it runs for is locked, removed or leaves the workspace, the bot stops and says "The person this bot runs for no longer has access." Choose someone else under Runs for, and the bot carries on by itself within a few minutes.
• Bots do not use a seat and do not appear in the members list.

4. Who may connect a bot

By default any member can approve a bot. A company admin can restrict this to admins in Settings › Security › Sign-in policy › Who can connect a bot. Anyone else then sees "Only a company admin can connect a bot in this workspace."

If your workspace has IP restrictions, they apply to bots too. A bot on an address that is not on the list cannot connect or run until the address is added.

5. Move a bot that signs in with a password

Older bots signed in with a person's email and password. On the bots list these show Password sign-in, and company admins get a reminder 14 days and 3 days before the cut-off naming the bots still left.

1. Update the bot to the latest version (from the bot page, choose Update to latest, or download it again).
2. Sign in on the bot once with Remember me ticked. The bot asks for its own key, deletes the saved password, and from then on uses the key. No code is needed if you are allowed to connect bots.
3. If that does not work, sign out on the bot and connect it with a code as in step 2.

After 26 October 2026 a bot that still uses a password is refused with BOT_KEY_REQUIRED. A current bot then shows the connect screen; an older one must be updated first.

6. Disconnect a bot

• On the bot's page in Automize, choose Disconnect. The key stops working within a minute. Do this straight away if a machine is lost or stolen.
• Signing out on the bot itself also disconnects it.
• A disconnected bot shows "This bot was disconnected. Connect it again." and the connect screen.

Connecting a machine again gives it a new key and cancels the old one.

7. Designing and recording in the bot app

When you record or design a process in the bot app, the bot asks you to approve a separate sign-in in your browser, with your own two-factor authentication. That work is saved as you, not as the bot, and the sign-in lasts at most 12 hours. Runs always use the bot's own key.

8. If it will not connect

For other bot problems, see Troubleshooting the bot.