Slack Bot - Not Reflecting Update Knowledge Base
I have created a Slack Bot with Voice Flow and a Replit App. However I have a couple of questions and issues.
1. My knowledge base refreshes everyday, will this reflect in my slack bot?
2. Even though I have updated my knowledge base and republished my Voice Flow project, the changes are not reflected in my slack bot - what could be causing this? how can I get it to refresh and reflect latest updates?
1 Reply
Hey! A Slack (or any) integration will only surface the version of your Voiceflow agent that it is calling through the Dialog Manager API.
1. Will a daily knowledge-base refresh show up automatically?
– Only if the version your Slack app is hitting is also rebuilt with those new documents. After you add / replace KB files you still need to compile or publish a new version of the agent so a new vector index is bundled with it.
2. Why are my KB changes not showing up?
The most common reasons are:
• Your Slack code is pointing at an old versionID (the long hash). Every time you click Publish Voiceflow creates a brand-new production versionID – if you keep the old one in your Replit code the bot will stay on the old KB.
• You updated the project but only hit Run (development). If your Slack app is sending
versionID: production, those changes won’t appear until you click Publish.
• Caching in the Replit process – after publishing, restart/redeploy the app so it pulls the latest settings.
Quick checklist to force-refresh:
1. Add / update your KB docs in Creator.
2. Click Run to test in development.
3. When happy, click Publish (green button) → this creates a new production version.
4. In your Slack/Replit code call the version by alias – versionID: "production" – or update the hard-coded versionID to the new one.
5. Redeploy / restart your Replit server.
Once the Slack bot is calling the new production version it will respond with the updated KB content.
Docs for reference:
https://docs.voiceflow.com/docs/versions-and-project-ids#updating-your-version