> ## Documentation Index
> Fetch the complete documentation index at: https://docs.relayhub.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Automation Wizard

> Build and fix automations by describing them in plain language

The Automation Wizard is a chat helper inside Automations. You tell it, in plain English, what you want an automation to do, and it builds it for you. You do not need to open the visual editor or know how the individual pieces fit together. If you can describe it, the Wizard can usually build it.

It works two ways: build a brand new automation from scratch, or find and change one you already have.

## Opening the Wizard

Go to the **Automations** in the left sidebar, then click the **Build with the Wizard** tab at the top of the page. The other tab, **My automations**, is the regular list of your flows.

<Note>
  The Wizard follows the same access as the rest of Automations. It is on by default, but your administrator can turn it off for specific users. If you do not see the tab, contact your admin.
</Note>

The Wizard has two sides:

* **On the left**, a chat where you describe what you want.
* **On the right**, a live preview of the automation as it takes shape, with a **Publish** button when it is ready.

## Building an automation from scratch

Just say what you want to happen. Be as specific as you can about when it should run and what it should do.

For example:

* "Every weekday at 9am, post 'Daily standup starting' to our Slack channel."
* "When a new file lands in a Google Drive folder, summarize it and email me the summary."
* "Every Friday at 4pm, remind me in Slack to submit my timesheet."

The Wizard reads your request, finds the right integrations, and starts building. If something is unclear, it asks a short question first, for example "Which email provider should I use, Gmail or Outlook?" or "Should that go to a channel or a direct message?" Answer in plain language and it continues.

When it finishes, the right pane shows a **draft** of your automation: what starts it (the trigger), the steps it will run, and which integrations it uses.

<Note>
  A draft is not live yet. Nothing runs until you publish it, and even then it stays turned off until you switch it on. You can always ask the Wizard to change the draft before you publish.
</Note>

## Reviewing and publishing

When the draft looks right, click **Publish**.

Publishing saves your automation, but it leaves it **turned off** on purpose. Nothing runs yet. This gives you a chance to connect the accounts it needs before it starts working. The preview lists the integrations the automation uses (for example Slack or Gmail) so you know exactly what to set up.

To finish turning it on:

<Steps>
  <Step title="Publish the draft">
    Click **Publish** in the preview. You will see a confirmation that the automation is saved and turned off.
  </Step>

  <Step title="Open it in the editor">
    Click **Open in editor**. This opens the automation in the visual editor.
  </Step>

  <Step title="Connect the accounts">
    Connect any accounts the automation needs, like your Slack workspace or Gmail. You do this the safe way in the editor. The Wizard never asks for passwords in chat.
  </Step>

  <Step title="Turn it on">
    Enable the automation in the editor. It is now live and will run when its trigger fires.
  </Step>
</Steps>

## Changing an automation you already have

You do not need to remember any IDs. Just name the automation and say what to change.

For example:

* "Change my 'Weekday 9am standup' reminder to run at 8am instead."
* "Add a step to my new-lead automation that also emails the sales team."

The Wizard finds the automation by name (if more than one matches, it will ask which one you mean), makes your change as a new draft, and shows it in the preview. Review it and click **Publish** when you are happy, the same as a new automation.

## The Wizard and the editor work together

Think of it this way:

* Use the **Wizard** when you want to build or change something quickly by describing it. It handles finding the right steps and wiring them together.
* Use the **visual editor** for the hands-on parts: connecting your accounts, turning an automation on or off, and fine tuning the details.

You can move between them at any time. The **Open in editor** and **Edit** buttons in the preview take you straight there.

## Tips for good results

* Say **when** it should run (a schedule, a new file, an incoming message) and **what** it should do. The clearer the request, the better the first draft.
* It is fine to build in steps. Start simple, look at the draft, then ask for changes like "also post it to the #general channel" or "only summarize PDFs."
* If the Wizard says an integration needs a connection, that is normal. Publish, then connect the account in the editor and turn it on.

## Next steps

* **[Automations](/integrations/automation-hub)** -- The full Automations, the visual editor, and running flows from chat
* **[Schedules](/integrations/schedule-hub)** -- Run automations on a recurring schedule
* **[RelayHub Assistant](/getting-started/relayhub-assistant)** -- Ask the in-product assistant how any feature works