Deploy & Rollback
This section covers how changes move to production and how to safely revert them.
🚀 Deploy (Publishing Changes)
A Deploy is the action of promoting your Draft version to Production.
What happens during a Deploy
Your Draft becomes the new live version
A version is saved in history (e.g., v23)
A new Draft is automatically created
⚠️ Impact of Deploy
When you can publish
The Deploy button is available only when the current Draft has pending changes.
If the Draft matches Production, the button is disabled. A tooltip explains that the Draft has no changes to publish.
Pending changes include:
Creating, editing, or removing Agents, Components, MCPs, Squads, Tasks, Tools, or Voices
Adding or removing Agent Tool, Agent MCP, or Squad Agent links
Selecting a previous version through rollback before publishing it
The Builder detects removals and unlinked entities. These changes count as pending even when no entity remains in the current Draft.
After an edit, the Builder marks the Draft as changed immediately. You do not need to reload before publishing.
🔎 Review changes before deploying
Before confirming a Deploy, review the version preview.
The preview compares your Draft with the current Production version. It groups each change as:
Added — an entity or relationship will be created
Removed — an entity or relationship will be removed
Changed — an existing entity has updated configuration
The preview includes Agents, Components, MCPs, Squads, Tasks, Tools, and Voices.
It also shows changes to Agent Tool, Agent MCP, and Squad Agent links.
For changed items, the preview shows the previous and new values. It highlights key fields, such as an Agent role or prompt, a Component value, a Task prompt, or Voice instructions.
The preview summarizes deployment impact. It is not a complete field-by-field history. Long values may be shortened.
Conversations
Ongoing conversations continue normally
New messages follow the updated behavior
Channels
If an Agent or Squad is removed:
The channel is automatically deactivated
The responder is unassigned
Responders
Removed Agents/Squads are no longer available
Channels depending on them stop working
📡 Channel Behavior
If the assigned Agent/Squad exists → works normally
If removed → channel becomes inactive
🔄 Rollback (Reverting Versions)
A Rollback restores your configuration to a previous version.
⚠️ Rollback is global and affects all versioned entities.
🔎 Review rollback changes
Before editing a previous version, review its preview.
The preview compares the selected version with your current Draft. It uses the same Added, Removed, and Changed groups as Deploy.
This lets you confirm the configuration impact before replacing the Draft.
How to Rollback
Open Version History
Select a version
Click Edit this version
Confirm
What Happens
The current Draft is permanently discarded
A new Draft is created from the selected version
You can review and deploy again
📌 Plan Limitations
Freemium → No rollback
Starter → 1 version back
Pro / Agency / Enterprise → Unlimited
⚠️ Restrictions
No partial rollback
Cannot rollback only one component
Cannot rollback to current Draft
🧾 Impact on CRM
CRM data is not versioned.
Preserved:
Tickets
History
Tags
Assignments
What changes:
Only Agent behavior
Workflow publishing and rollback
Workflow publishing follows its own save and publish states:
Editing with unsaved changes
Available
Disabled
Saved and matching Production
Disabled
Disabled
Saved as Draft with unpublished changes
Disabled
Available
When Publish is available, selecting it publishes the saved Workflow directly without opening an additional confirmation page.
Use the history icon beside Publish to review earlier versions. In version history, the Publish action appears only when the selected version is different from the version currently in Production.
✅ Key Takeaway
Deploy makes your changes live
Rollback safely restores previous versions
Neither affects stored data or conversation history
Last updated