HighLevel
Log in
Roadmap
Feedback
Changelog
←
Back to changelog
Powered by Canny

new

Automations

Version History in AI Builder

Overview
The Workflow AI Builder now tracks every iteration it creates. Each AI build or edit produces an artifact card in the chat, and any of them can be restored in a single click.
Built-inRetinaDisplay-ezgif
What's New
  • Artifact card for every AI iteration: Every build or edit from the AI Assistant produces a card inline in the chat, at the point where the change was made.
  • Current version indicator: The card matching the canvas carries a purple border, so the active iteration is always identifiable.
  • One-click restore: Open the three-dot menu on any older card and select "Restore this version." The canvas reverts instantly.
  • Bidirectional and non-destructive: Restoring an older iteration keeps newer ones restorable. Iterations can be moved between freely, and none are destroyed.
  • Unsaved indicator: When auto-save is off for the location, cards display an "Unsaved" pill until the workflow is saved manually. The pill does not appear when auto-save is on.
  • Synced with Version History: "Show in version history" opens the Version History tab, where AI and manual versions appear in one unified timeline. Version History remains the single source of truth for version numbering.
How to Use
  1. Prompt the AI Assistant to build or edit your workflow.
  2. An artifact card appears in chat with a purple border marking it as the current version.
  3. Prompt another change. The new card takes the border, and the previous card gains "Restore this version" in its three-dot menu.
  4. Use the three-dot menu on any card to restore that iteration or open it in Version History.
Why This Matters
AI edits previously had no recovery path - a removed trigger or an overwritten action config meant rebuilding by hand. Tying every AI iteration to a restorable artifact makes the assistant safe to experiment with: bold edits can be attempted, compared, and rolled back without leaving the conversation or losing work. Routing those iterations into the same timeline as manual versions keeps Version History authoritative rather than splitting AI and human changes into parallel histories.