Testing and publishing
Test GiovBot privately, publish your draft, roll back a bad update within 24 hours, and move agents between workspaces as JSON.
On this page
Every change you make to an agent is saved as a draft first. Visitors keep getting the published version until you publish again.
Drafts
Each studio page has Save draft. Saved changes stay in the draft until you publish. The studio header shows Unpublished changes when the draft differs from what's live.
A publication includes:
- the agent's settings, first message and system prompt
- its procedures and tools
- its own variables
- which knowledge sources are attached
Workspace variables and the content of shared knowledge sources belong to the workspace. Changes to them apply straight away, without publishing. For example, resyncing a website updates every agent that uses it.
To throw away your draft, choose Discard in the studio header. This restores the last published configuration and can't be undone.
Test your agent
Draft chat
Choose Preview in the studio header to chat with the draft. Nothing is saved. If your prompts use variables such as {{name}}, set test values for them under Variables.
The Try it step of the setup guide has the same kind of private chat. It also shows which knowledge sources each reply used, and flags replies that would bring in your team or had too little knowledge to answer.
Test scenarios
Scenarios check that your agent keeps behaving the way you expect after each change. Open GiovBot → your agent → Tests and choose Add scenario.
| Field | What it checks |
|---|---|
| Visitor message | The message to send, for example "I want a refund" |
| Reply contains | Text the reply must include, for example "order ID" |
| Must not contain | Text the reply must not include, for example "I don't know" |
| Expected handoff | Any, Must hand off or Must not hand off |
| Expected procedure | The procedure that should be triggered |
| Expected tool | The tool that should be called |
| Mock HTTP response | Optional. A stand-in response for the tool, so the test doesn't call your real system |
Choose Run on one scenario, or Run all. Each scenario shows Pass, Fail or Not run, and when it last ran. Scenarios run against the draft, so run them before you publish.
Draft chats, Test RAG questions and scenario runs share a limit of 500 runs a month per workspace.
Publish
Choose Publish in the studio header. The new version goes live straight away on every channel that uses this agent.
- The workspace switch Allow published agents to reply must be on for any agent to answer. See GiovBot.
- On Pro, and on Starter with the GiovBot add-on, one agent can be live at a time. To publish another one, deactivate or archive the live agent first, or upgrade to Business or Advanced.
- Deactivate agent in the agent's Settings stops its replies immediately and keeps its draft and history. Activate in the studio header publishes it again.
Version control
GiovBot → your agent → Version control lists every published update with its version, date and type: a published update or a rollback. Agents that were published before version history existed start with an Existing publication entry.
Roll back within 24 hours
If an update goes wrong, you can restore the version before it:
- Open Version control. The latest publication shows its rollback window.
- Choose Roll back on it and confirm.
The rules:
- You can roll back only within 24 hours of the latest publication.
- You can roll back once, and only to the version immediately before it.
- Rolling back restores the settings, tools, procedures, variables and knowledge source assignments. Unpublished draft changes are discarded.
- The rollback is recorded as a new entry. It doesn't open a new 24-hour window.
- If a knowledge source that the earlier version used has since been deleted, that version can't be restored.
Export and import
Use JSON export to keep a copy of an agent, or to copy it into another workspace. Both options are in GiovBot → your agent → Settings → Import and export.
Export
Choose Export agent JSON. The export is taken from your saved draft, so save any changes first.
| Included | Not included |
|---|---|
| Agent settings, first message and system prompt | Uploaded files themselves (their extracted text is included) |
| Variables, procedures and tool definitions | Activity and conversation logs |
| Knowledge source definitions with their extracted text | Publication history |
| Test scenarios | Provider keys, tool authentication values and signing secrets |
Import
- Open the agent you want to replace and choose Import agent JSON. Browse for the file or drag it in. Files can be up to 20 MB.
- Confirm. The file replaces this agent's draft and its resources. The published version stays live.
- Review the imported agent, then publish.
Before you publish an imported agent, check:
- Tool credentials. Newly imported tools have no credentials, and their write access is off until you configure them. Tools that match ones this agent already has keep their stored credentials.
- Handoff and transfer targets. Teammates, departments and agents from another workspace don't exist here, so set them again.
- Variables. Workspace variables in the file become variables of this agent.