Choose the support source
Published stories and selected fields. Select content that answers real customer questions rather than importing every resource in the account.
Integrations Storyblok
StoryblokKnowledge connector
StoryblokKnowledge connectorPublished stories. Consistent support answers.
Bring selected published Storyblok content into Message knowledge, with the region and content fields configured for your support material.
A provider-specific knowledge adapter exists. Your source configuration, access and content approval determine what can be used. Connecting a source does not make all of its contents public.
Knowledge
Make the connection useful.
- 01Storyblok
- 02Review selected content
- 03Message AI knowledge
Keep source boundaries intact
Use the published-content path. Keep preview tokens and unapproved internal fields out of customer-facing knowledge.
Review the customer answer
Ask a question supported by the selected source and one it cannot answer. Review the retrieved content and the response before enabling customer-facing use.
The right context
Be precise about what connects.
Define the data, permissions and destination before putting the workflow in front of customers.
Included content
Published stories and selected fields.
Connection configuration
Content delivery token, region and field mapping.
Access boundary
Use the published-content path. Keep preview tokens and unapproved internal fields out of customer-facing knowledge.
Your setup path
Start with one working flow.
- 01
Configure the source
Open Message’s data connector settings. Configure content delivery token, region and field mapping.
- 02
Review the preview
Preview published stories and selected fields. Remove unsuitable sources and approve only material intended for your customers.
- 03
Check the result
Test a known answer, an unknown question and a source update. Verify that the assistant uses the correct workspace’s approved knowledge.
Before you connect
Storyblok integration questions
What does the Storyblok connector read?
Published stories and selected fields. Use the published-content path. Keep preview tokens and unapproved internal fields out of customer-facing knowledge.
Does connecting a source immediately publish its content?
No. Review the source preview and approve the material intended for customer answers. Access to a source is separate from permission to publish its contents.