Build with

Use help-desk articles as an approved source for your agent’s answers. The worked example imports Zendesk Help Center articles. The same review and verification steps apply when another provider supplies public URLs or approved text.

Before you begin

  • A test Voiceflow project with Knowledge enabled for the agent.
  • A content owner who can approve the articles, audience and update process. Exclude private tickets and customer records from general support answers.
  • For Zendesk, access to authorize the Help Center and select its brand and article filters. This connection is separate from Zendesk ticket tools.
  • Two questions with answers in the chosen articles, and one question outside their scope.

Studio

Open Agent studio and choose the project that will use the articles.

Code

Use a Voiceflow bearer credential with access to the test project and Environment. Keep it on your backend or development machine. Set:

Install the current Voiceflow CLI if you choose CLI. Both examples below use VF_TOKEN. Standalone tool execution uses the Environment’s Draft; it does not attach a tool to an agent or publish it.

Import and check the source

1

Choose the import path

Article lookup through an API or MCP tool is different from importing content into Knowledge. The walkthrough below uses the Zendesk source.

2

Open the Knowledge connection

Open Agent studio, select the same project used by your agent or code, then open Build → Knowledge base → Add data source → Zendesk. Enter the Help Center’s Subdomain URL, select Connect and complete authorization.

Open Knowledge base in the project that will use these articles. Photo:
Authorize the Help Center separately from ticket tools. Photo:
3

Select the articles and start the import

In Import from Zendesk, choose the required Brand. Narrow Locales, Categories, Labels and User segments to the approved content. Check the matching article count before continuing. Select the destination Folder, structure and metadata choices. Choose Refresh rate here too: Never leaves updates manual; scheduled rates require the workspace’s Knowledge refresh entitlement. Then click Import data sources.

Check the selected brand, filters and article count before importing. Photo:

Wait for processing to complete. A successful account connection or a nonzero article count is not a completed import.

4

Inspect an imported article

Studio

Find one expected article in Knowledge base and open it. Compare its content and metadata with the provider source; check that the title, language and relevant policy facts are present.

Code

Locate the article in documents[], retain its Voiceflow id and wait for status.type: "SUCCESS". PENDING and INITIALIZED are not completion; inspect an ERROR. The Voiceflow document ID differs from the provider article ID.

5

Verify retrieval and the agent's answer

Studio

Return to Agent and run one of your article questions with Knowledge available. Compare the answer and retrieved source with the original article. Test the out-of-scope question too; the agent should follow your configured fallback rather than invent policy.

Code

Run a Draft retrieval diagnostic for a question actually covered by the imported content:

Compare answer.chunks[].documentID, source and content with the imported article. With synthesis: false, answer.output is null. This is a build-time diagnostic; also run a Draft conversation to verify the agent’s actual answer and fallback.

Keep answers current

Assign an owner for content changes. For a Zendesk managed source, choose the appropriate Refresh rate during import. Open the resulting Zendesk source entry and use Sync to verify an update. Review filter changes, excluded articles and restoration when changing its coverage; a sync can remove articles that no longer match its filters.

For URL or text imports, follow that provider’s documented refresh or replacement procedure. Importing an article does not, by itself, establish ongoing synchronization.

Verify the import

  • The expected articles have completed processing and contain the approved content.
  • Both in-scope questions retrieve the right source and receive answers consistent with it.
  • The out-of-scope question follows the agent’s fallback.
  • A changed source has an assigned update path and owner. Before deployment, publish the reviewed Environment and repeat the answer check in a fresh customer session.

An expected article is missing

Check selection and processing before importing the same content again.

Confirm the provider account, brand, language and filters. Locate the original article, then look for it in the same Voiceflow project and Environment. If it is present but retrieval is wrong, inspect its actual chunks and the agent’s Knowledge configuration. A working ticket tool does not verify a Knowledge import.

Use the up and down arrow keys to select a result, Enter to open it, and Escape to close the search.