Deploying to Production

Editing never changes any environment. Only a deploy changes what runs.

Versions

Publishing a chatbot, agent or workflow creates an immutable version. Development and Production each point to one version; the project overview shows how far Production is behind.

Deploy

1. 01
   Test in DevelopmentYou are here

   Deploy to Development and try it there.

   Deploy the version to Development and test it: the Playground, test cases, the Development preview, or a workflow's Execute mode.

   Mark as done
2. 02
   Deploy to Production

What gets checked depends on the resource: required knowledge sources must be ready, required integrations connected, required secrets set in that environment.

Credentials stay in their environment

Secrets, connections and API keys are bound to one environment. A Development key can't reach Production, and a deploy never copies credentials. Set Production's own before you deploy there.

Roll back

Pick an earlier version and deploy it again. Chatbots also have one-click restore in Deploy and versions.