Agent setup guide
Knowledge Base Builder
Turns docs, email threads and answered questions into reviewed knowledge-base articles in Notion.
What it does
Turns docs, email threads and answered questions into reviewed knowledge-base articles in Notion.
- Receives material through a webhook: a document's text, an email thread, a chat thread, a resolved support answer or meeting notes.
- AI decides whether it holds reusable knowledge and, if so, writes a clear article (how-to, SOP, FAQ, policy, troubleshooting, reference) with a summary, tags, who to ask and the source.
- Flags ambiguous or outdated points as questions to confirm, marks sensitive content, and strips passwords and keys.
- Every article waits in Reviews; once a teammate approves it, it's added as a page to your Notion knowledge-base database and announced in your Slack channel with a link to the page.
- Material with nothing reusable is kept in the run history with the reason.
What it needs
- A paid plan (agents run live on paid plans).
- An AI provider key (Settings → AI Providers).
- Notion and Slack, connected in Settings → Integrations.
- A way to send text to a webhook (a form, a script, or another workflow).
What it doesn't do
- It doesn't crawl Google Drive, your inbox or websites by itself, and it can't read audio, images or scanned PDFs. It works from the text you send.
- It doesn't update or merge existing articles; each approved item becomes a new page.
- It doesn't answer questions from the knowledge base.
Availability and plans
Available
Its workflow is built and tested, and every app it needs is live. You can get it and set it up now.
Included free on the Elite and Enterprise plans; on other paid plans it's a one-time purchase per workspace (the price is on the Agents page). The Agents page in the app always shows its current status.
Before you start
- A paid plan: agents run live, and the Free plan only runs Dry Runs.
- An AI provider key (OpenAI, Anthropic, Google and more) in Settings → AI Providers. AI usage is billed by your provider.
- These apps, connected in Settings → Integrations: Notion and Slack.
- A form, app or system that can send each new item to a webhook URL (the agent starts from a webhook).
- About 15 minutes.
Set it up step by step
Get the agent first (buy it, or it's already yours when your plan includes it), then in Agents → My agents press “Set up this agent”. That creates the agent's workflow in your workspace (it counts towards your plan's workflow limit) and opens the canvas with a setup checklist above it. Each item links to the exact place to go and ticks itself off when it's done.
1. Connect your AI provider
The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
2. Connect Notion
Connect the Notion workspace that holds your knowledge base (Settings → Integrations → Notion) and share the database with it.
3. Connect Slack
Connect the Slack workspace your team uses (Settings → Integrations → Slack).
4. Describe your team and readers
Open “Draft the knowledge-base article” and replace the placeholder, so articles use your terms and suit your readers.
| Setting | What to enter | In step |
|---|---|---|
| Your team and readers | Replace the placeholder in the AI step's instructions with who you are, who reads the knowledge base (new hires, support agents, customers) and the product or internal terms they use. It starts as “[DESCRIBE YOUR TEAM AND WHO READS THE KNOWLEDGE BASE HERE]” until you replace it. | “Draft the knowledge-base article” |
5. Pick your knowledge-base database
Open “Add the article to Notion” and pick your account and database.
| Setting | What to enter | In step |
|---|---|---|
| Notion account | The Notion workspace the articles are added to. Pick your connected Notion account. | “Add the article to Notion” |
| Knowledge-base database | Pick the Notion database your knowledge base lives in (share it with the Fluxo Flow integration first). Its title column should be called “Name”, Notion's default. | “Add the article to Notion” |
6. Pick the Slack account and channel
Open “Announce it in Slack” and pick your account and channel. Invite the app to private channels first (/invite @Fluxo Flow).
| Setting | What to enter | In step |
|---|---|---|
| Slack account | The Slack workspace new articles are announced in. Pick your connected Slack account. | “Announce it in Slack” |
| Channel for announcements | Pick the channel where your team should hear about new articles, e.g. #general or #knowledge. | “Announce it in Slack” |
7. Test it with Dry Run
Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
8. Switch the trigger on
Open the trigger, switch the webhook on and send material to its URL (title, source, link and the text as “content”).
How it works
The agent is a normal workflow with 7 steps (1 AI step, with a person approving in Reviews). You can open, edit and monitor it like any other workflow.
- New source material — Starts when your form or app sends data to the agent's webhook URL. A document's text, an email thread, a resolved support answer or a Slack thread is posted to the workflow's webhook URL (from a form, a script or another workflow).
- Draft the knowledge-base article — AI step (runs on your AI provider key). AI decides whether the material holds reusable knowledge and turns it into a clear article (how-to, SOP, FAQ, policy…) with a summary, tags and points to confirm.
- Worth adding? — Decision: picks the branch to follow. Material with no reusable knowledge is kept in the run history; everything else goes to review.
- Review the article — A person approves or rejects it in Reviews (the run waits). Branch: Article. A teammate checks the draft in Reviews (especially points to confirm and anything marked sensitive), edits it and approves it to publish.
- Add the article to Notion — Notion: Create a page in a database. Branch: Approved. Creates the article as a page in your knowledge-base database, with its summary, body, tags and source.
- Announce it in Slack — Slack: Post a message. Once the page is created, tells your team a new article is in the knowledge base, with its title, summary, tags and a link to the Notion page.
- Not added — Kept in the run history. Branch: Nothing reusable. Material with nothing reusable is kept in the run history with the reason.
Test it with Dry Run
Press Dry Run in the canvas. The agent runs on the sample data stored on its trigger (the “Sample data for Dry Run” box), so you can check every step's output before anything is live. Edit the sample to match the fields your own form or app sends.
Sample data fields
title, source_type, source_url, author, content.
- Nothing is sent or written: app actions, emails and Slack posts are simulated, and AI steps don't call your AI provider.
- Approval steps use the Dry Run decision you pick in the step's settings (approved, rejected or timeout), so you can try each branch.
Go live
- Open the trigger, switch the webhook on and send material to its URL (title, source, link and the text as “content”).
- The webhook is protected by a secret: send it in the header shown in the Activation panel (requests without it are refused with 403). Each request starts one run.
- The setup checklist adds a “paid plan” item before activation: live runs need a paid plan (the Free plan only runs Dry Runs).
- When every checklist item is done and the trigger is on, the checklist says “Live — this agent is running”. Follow its runs in the workflow's History tab and in Analytics → Agents.
Questions
Is anything published without a person checking?
No. Every article waits in Reviews until a teammate approves it.
Can it pull documents from Google Drive or my inbox by itself?
Not in this version. Send the text to its webhook, for example from a form, a script, or another workflow.
Troubleshooting
- “No AI provider connected” or a rejected key: connect or fix the key in Settings → AI Providers, then press Test there.
- A checklist item stays unticked: the setting is still empty or still contains its placeholder text. Open the step from the checklist and fill it in.
- An app step fails with “Needs reconnect”: the account's access was revoked or expired. Reconnect it in Settings → Integrations.
- Slack says the app isn't in the channel: in Slack, type /invite @Fluxo Flow in that channel (always needed for private channels).
- Nothing happens when your form sends data: check the webhook is switched on and the request carries the secret header (403 means it's missing or wrong).
- A run shows as paused: it's waiting for someone in Reviews to approve or reject it.
- A step failed: open the run in History and check that step in the Trace tab for the error and what it received.
Generated from the agent's own workflow, so it always matches what the agent does. Last updated .