Create knowledge base docs from webhook URLs and assign to conversational agents

Post a page URL and a name to a FlowMattic webhook, and ElevenLabs creates a knowledge base document from that URL, then updates a conversational agent with the new document.

Webhook

ElevenLabs

Download this workflow Browse more workflows

3 steps Setup ~5 min Used on 1.9k sites Free to import

The Create knowledge base docs from webhook URLs and assign to conversational agents workflow on the FlowMattic canvas, with 3 steps across Webhook, ElevenLabs — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

A voice or chat agent in ElevenLabs answers better when its knowledge base holds your latest help articles, product pages or policies. Adding each page by hand gets skipped when you're busy. This workflow lets any system that can send a webhook, a CMS, a script or another automation, add a page to the knowledge base and hand it to an agent in one request.

Runs start at the Webhook trigger's own address. The template expects two values in the request: url, the page to learn from, and name, the title the document should get. Senders that use other keys need the mapping changed after import. To stop strangers from starting runs, turn on the trigger's "Require authentication on incoming requests" setting.

The first ElevenLabs step creates a knowledge base document from the URL, under the name you sent. The second step updates an existing agent's configuration, passing it the new document's ID and name with the type set to URL. The template doesn't say which agent: you choose it when you set up the Update Agent step, and every run updates that same agent.

Try it first with a test agent. Afterwards, check the agent's knowledge base in ElevenLabs to confirm how the new document sits next to the ones it already had, and use Task History to see what each step returned.

Help articles reach the support agent

When a new help article goes live, the site posts its URL to the webhook so the ElevenLabs support agent can draw on it in its next calls.

Product pages for a sales assistant

A store sends each new product page to the webhook, and the agent that answers pre-sales questions gets a knowledge base document for it.

Policy updates for a phone agent

An office manager posts the URL of a revised returns or booking policy, so the voice agent answering the phone works from the current page.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Webhook Capture Webhook Response
Waits for a request at the workflow's webhook URL. The template reads two keys from it, url and name, so the sender must include both or you remap the next step to the keys it does send.
Step 2Action
ElevenLabs Create Knowledge Base Document
Creates an ElevenLabs knowledge base document from the URL in the request and names it with the name value. ElevenLabs returns the document's ID and name for the next step.
Step 3Action
ElevenLabs Update Agent
Updates an existing ElevenLabs agent, passing the new document's ID and name with the document type set to URL. Choose the agent when you set up the step; the template leaves that to you.

What you need

FlowMatticCore
ElevenLabs AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Turn on "Require authentication on incoming requests" in the Webhook trigger and give the key only to the system that sends pages, so no one else can add documents to your agent.
Run one test with a spare agent and check its knowledge base in ElevenLabs afterwards, so you know whether earlier documents stay attached before you point the workflow at a live agent.
For several agents, put a Router between the Create Knowledge Base Document and Update Agent steps, one route per agent, each with its own Update Agent step. Use conditions that can't both match, such as distinct values of a key you send.

Questions about this workflow

What must the webhook request contain for ElevenLabs?

A url key with the page address and a name key with the document title. Those are the two values the template maps into the Create Knowledge Base Document step.

Which ElevenLabs agent gets the new knowledge base document?

The one you select in the Update Agent step after import. The template doesn't name an agent, so every run updates that one agent. To serve several, put a Router between the Create Knowledge Base Document step and the Update Agent step.

Can anyone who finds the webhook URL add documents?

Not if you turn on the Webhook trigger's authentication setting. With it on, a request needs the key you set, so only your own systems can start a run.

Does the agent keep its earlier knowledge base documents?

Check that on a test agent before going live. Look at its knowledge base in ElevenLabs after a run, and see the Update Agent response in Task History.