Skip to main content
Deployment is when a tested agent is allowed to operate in a real workflow. In V3, deployment means publishing the agent configuration and confirming its triggers, tools, and behavior controls.

Publish Changes

Agent edits are staged before they affect production behavior. When the save bar appears, review the change and publish intentionally. Before publishing:
  • Test the agent in Sandbox.
  • Confirm the right Skills are assigned.
  • Confirm tool access is narrow and correct.
  • Confirm Behavior settings match the automation level you want.
  • Confirm escalation rules are in place.

Triggers

Customer agents deploy through an inbox trigger. Open the agent sidebar and confirm which inbox the agent listens to. Internal agents deploy through internal triggers such as Slack channels when available for your workspace. Disabled trigger rows should not be treated as active automation.

Automation Levels

Teams usually progress through these operating modes:

Safety Controls

Use these controls to expand automation gradually:
  • Escalation rules for cases that must go to a human
  • Conversation tags for categorization and urgent-message handling
  • Working hours for when the agent should operate
  • Response delay so humans have time to review before auto-send
  • Auto mark-as-done for completed conversations
  • Tool access scoped to the agent’s actual job
  • Activity review after publishing
By repeating the Connect > Teach > Test > Deploy loop, you can expand what the agent handles without losing oversight.