Build with AI

Build with AI turns a description into a proposed Workflow or proposes changes to the Workflow you have open. Review the proposal, connect the actual accounts and resources, and test the result before relying on normal execution.

The builder assistant is different from an AI Step. The assistant helps configure the graph; an AI Step calls an AI service when that Step executes.

Describe a new automation

Open Workflows → Create workflow. If the assistant is not open, select Build with AI. In Describe your workflow, explain the event that starts work, the apps involved, and the desired result, then select Send.

A useful request is:

Text
When a new paid order arrives in Shopify, add one row to Google Sheets.
Include order ID, customer name, total, and currency.
Skip unpaid orders. I will choose the spreadsheet and connect accounts in the editor.

Include conditions, the intended handling of lists, and any delay or duplicate rule. Use exact app names and describe the result rather than assuming the assistant knows your private workspace or resource identifiers.

Your messages are processed by AI providers. Connect accounts through the editor; do not paste passwords, API keys, or tokens into the chat. Use fictional sample data when private customer details are not needed.

Review before creating

Inspect Workflow draft preview and Review changes. Check the Trigger, Steps, route order, mappings, required fields, and any assumptions about event or Action capabilities. View proposed configuration exposes the proposed document for closer inspection.

You can edit Workflow name without generating the graph again, or describe a change in the chat to refine the proposal. Choose Discard proposal if it should not be applied.

Select Create draft to create the proposed inactive Workflow. Creation does not activate it. If you opened the assistant inside an empty Workflow with no Trigger, the proposal can be created as a separate Draft while the empty Workflow remains unchanged; read the explanation beside the button.

The assistant can use integration schemas and may show synthetic sample checks for generated Code. Those checks are not a live provider test and do not prove the connected account can access the intended resource.

Finish setup in the editor

After creating the Draft:

  1. Open the Trigger and each Action, select a compatible account, and finish authorization where needed.
  2. Choose real resources such as the sheet, channel, project, or list. Review dependent selections after changing an account.
  3. Select representative Trigger test data and check every important mapping.
  4. Test conditions and Actions with suitable test destinations.
  5. Activate only when ready, then generate a fresh event and inspect its run and provider result.

An Action test can make real changes while the Workflow is a Draft. Auto-validate can also execute real Actions and AI calls. Follow Workflow testing, Connected accounts, and Data mapping.

Change an existing Workflow

Open that Workflow and select Build with AI. Describe the specific change and what should remain: for example, add a paid-status Filter before the current message Action while keeping its channel and message mappings.

The chat edits the current Workflow. To create another automation, start from Workflows instead of assuming a request in this chat creates a separate copy.

Review the proposed changes against the selected Workflow. On a Draft or paused Workflow, Apply changes saves the proposal without activation. On an active Workflow, the button is Publish changes: applying it updates the active automation. Existing work keeps running until the changes are published.

For a significant change, consider an export or separate Draft, inspect the proposed removals and mappings, and test the revised configuration deliberately. Applying an AI proposal is not a substitute for verifying the resulting Workflow version and run behavior.

Clear, close, and recover the conversation

Close assistant hides the panel. Clear chat clears the conversation and proposal; it does not delete the selected Workflow or undo changes already applied. Check the current canvas when returning to the assistant rather than assuming the conversation is the saved configuration.

If generation fails, Retry request retries the assistant request, not an Action or Workflow run. If saving reports an error, inspect the editor's current state before creating another copy. Resolve a changed or stale Workflow baseline by reviewing a fresh proposal against the current graph.

For execution failures after setup, use Run history and Workflow retries.