# Build an automation with Orbit > Describe an automation in plain language, review the plan Orbit drafts, save it, test it and open it in the editor. Nothing runs until you activate it. Canonical: https://help.spacebrain.ai/automations/build-with-orbit/ Last modified: 2026-09-25T00:00:00.000Z Orbit, Spacebrain's AI assistant, can turn a sentence like "When a form creates a lead, email them and create a follow-up task" into a draft automation. You review the plan, save it as a draft, then test and publish it when you're ready. This guide is for anyone who wants a working first draft without placing every step by hand. ## Before you begin [#before-you-begin] * **Permission:** you need editing permission in the workspace. Without it, the builder shows **You need editing permission in this workspace to build or change automations.** * **Credits:** building with AI uses credits. If you run out, you'll see **Add credits to keep building automations with AI.** * **Connections:** if the automation will send email, texts or calls, connect those accounts first under **Automations → Connections**. Orbit can still build the draft without them, but it leaves the missing settings for you to fill in. * **Know your trigger:** write down what should start the automation (for example "a form is submitted") and what should happen, in order. > **Note — Nothing runs until you activate it** > > Orbit only creates or changes drafts. Publishing is always a separate step that you confirm. ## Where to find it [#where-to-find-it] You can build with Orbit from two places: * **Automations → Overview:** the **Build automations with AI** panel is at the top of the page. * **Automations → All Automations:** choose **New Automation**, then **Describe with Orbit**. The **New Automation** button on a module's own Automations page (for example **CRM → Automations**) opens the manual starter list instead. To use Orbit, go to the main **Automations** pages. ## Build a new automation [#build-a-new-automation] 1. In the builder, make sure **Create new** is selected. 2. Type what you want in **Describe your automation**. Include the trigger, each action and any timing. You can also choose an idea under **Start with an idea**, such as **Review each new lead** or **Follow up after a webinar**, and edit the text. 3. Select **Build automation**, or press Ctrl + Enter (⌘ + Enter on a Mac). 4. Wait while Orbit works. You'll see progress such as **Understanding your request** and **Connecting triggers and actions**. Select **Stop** if you want to change your request. 5. If Orbit needs more detail, it shows **A question before we continue**. Type your answer and select **Send reply**. 6. Review the plan. It's marked **Draft plan** and shows: * **Starts when:** the trigger. * **Actions & steps:** each step in order, including waits such as "Wait 1 day". * **Finish setup in Automation setup:** any settings you still need to choose, such as a sender or a task owner. * **Plan details:** how many steps and connections will be added, and any notes. 7. To change the plan, type in **What would you like to change?** and select **Update plan**. Try the suggestions **Add an SMS follow-up**, **Adjust the timing** or **Add an AI phone call**. 8. When the plan looks right, select **Save draft**. 9. You'll see **Draft saved. Continue here to inspect, test or request activation.** Select **Open saved automation** to open the draft in the editor. ### Example request [#example-request] > When the Contact us form is submitted, add the tag website-enquiry, create a task called "Call new enquiry" for the lead's owner due in one day with high priority, then wait one day and send the "Thanks for getting in touch" email. A good request names the form, the tag, the task details, the wait and the email. The more specific you are, the fewer follow-up questions Orbit asks. ## Test and publish from the same conversation [#test-and-publish-from-the-same-conversation] After you save, you can keep talking to Orbit in the same panel. For example, ask it to test the draft or publish it. Orbit prepares each request as a proposal, and you confirm it with a button: | Button | What it does | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------- | | **Run metered Auto test** | Runs an automatic test of an AI conversation step. Messages and bookings stay simulated, and the result shows the credits used. | | **Publish & activate** | Publishes the draft so it runs on real events. | | **Pause automation** | Stops new runs of a live automation. | You can also finish in the editor instead. It's often easier to check setup there. See [Build an automation in the editor](/automations/workflows/) for **Setup**, **Issues**, **Test** and **Publish**. > **Warning — Publishing doesn't prove delivery** > > After publishing, Orbit reminds you that publication does not prove message delivery or a booking. Check the first real runs under **Automations → Runs**. ## Change an existing automation [#change-an-existing-automation] 1. In the builder, select **Edit existing**. 2. Choose the automation. You can search with **Search by automation name…**. 3. Describe the change in **Describe your changes**, for example "Wait two days instead of one. Keep the other steps unchanged." 4. Select **Plan changes** and review the plan. 5. Select **Apply changes**. If the automation is live, the published version keeps running while you edit. Your changes only go live after you publish them. If a plan would switch a live automation back to a draft, Orbit warns you: **Applying this plan stops new runs of the live automation until you activate it again.** ## What you should see [#what-you-should-see] * A draft appears in **Automations → All Automations** with the status **Draft**. * **Open saved automation** opens that draft on the editor canvas, with the trigger and steps from the plan. * Any settings Orbit couldn't fill in are listed under **Setup** in the editor. ## If something goes wrong [#if-something-goes-wrong] | What you see | What to do | | ---------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | **AI could not turn that request into an automation plan.** | Add a clear trigger ("When…") and at least one action, then try again. | | **This plan is no longer usable…** and a **Rebuild plan** button | The workspace or automation changed since the plan was made. Select **Rebuild plan**. | | **We could not verify whether the draft was saved.** | Don't build again straight away. Select **Check automations** to see whether the draft exists, then choose **I've checked automations — start over**. | | **Add credits to keep building automations with AI.** | Add credits, or build the automation manually instead. | | **Too many requests. Wait a moment before saving again.** | Wait a few seconds and select **Save draft** again. | | The plan lists setup issues | Save the draft, open it in the editor and complete **Setup**. | To start again at any time, select **Start over**. ## FAQ [#faq] ### Will Orbit send anything while it's building? [#will-orbit-send-anything-while-its-building] No. Orbit only creates or changes drafts. Messages are sent only after you publish the automation and a real event triggers it. ### Can Orbit fix a failed run? [#can-orbit-fix-a-failed-run] Yes. On a failed run's details page, select **Prepare AI repair**. Orbit proposes a repair as a draft. It does not replay the failed run. See [Runs and troubleshooting](/automations/runs-and-troubleshooting/). ### Can I also ask Orbit from the Orbit panel? [#can-i-also-ask-orbit-from-the-orbit-panel] You can ask Orbit about your automations from the Orbit panel too. Building and editing drafts step by step works best in the **Build automations with AI** panel. See [Orbit, your AI assistant](/platform/orbit-assistant/). ## Next step [#next-step] Open your saved draft and finish it in [the editor](/automations/workflows/): complete **Setup**, run a dry **Test**, then **Publish**.