Help Publish Agent via API URGENT
I’m working on a project where we used the Voiceflow API and Knowledge Base API to create a custom agent embedded in a front end. We also added buttons on this front end to dynamically update the knowledge base.
However, I just realized that these updates don’t actually take effect until we manually go into Voiceflow and publish the agent, which defeats the purpose of dynamic updates.
Is there a way to trigger a publish via API or bypass this limitation? Would love any suggestions or workarounds!!
1 Reply
Hey – quick clarification on how versioning works:
• The Knowledge Base Management API saves the doc right away, but your agent’s production build is frozen at the last time you hit “Publish.”
• Today there’s no REST or CLI endpoint that can trigger that Publish action – it can only be done from the Creator UI. Work-arounds you can use now 1. Point your requests to the development version instead of production. • When you call the Dialog Manager API, add a header: (or include
• The development alias always reflects the latest flow + KB changes without needing a publish. 2. If you still need a locked “prod” build, automate a publish step outside VF (e.g. a small script that notifies a teammate to press Publish, or a headless-browser job), but there isn’t an official API for it yet. 3. Alternative pattern: keep the agent flows in production, but fetch your KB answers with the Knowledge Query API in real-time and pass them to the agent as a tool/function. That way the agent doesn’t depend on the compiled KB. Summary At the moment publishing can’t be triggered programmatically; switching your integration to
• Today there’s no REST or CLI endpoint that can trigger that Publish action – it can only be done from the Creator UI. Work-arounds you can use now 1. Point your requests to the development version instead of production. • When you call the Dialog Manager API, add a header: (or include
?versionID=development for websocket/chat-widget).• The development alias always reflects the latest flow + KB changes without needing a publish. 2. If you still need a locked “prod” build, automate a publish step outside VF (e.g. a small script that notifies a teammate to press Publish, or a headless-browser job), but there isn’t an official API for it yet. 3. Alternative pattern: keep the agent flows in production, but fetch your KB answers with the Knowledge Query API in real-time and pass them to the agent as a tool/function. That way the agent doesn’t depend on the compiled KB. Summary At the moment publishing can’t be triggered programmatically; switching your integration to
versionID: development is the simplest way to have your dynamic KB updates reflected immediately.
Docs: https://docs.voiceflow.com (see “versionID header” in the DM API section).