Knowledge Management Integrations

Use Knowledge Management integrations to allow Biggy to read, update, and create knowledge articles.

When the Create Knowledge Page action is enabled, Biggy can create new pages in your knowledge tools.

Multi-integration configuration

You can configure multiple instances of the same type of knowledge management integration.

To add an additional integration, click + New Instance on the integration configuration page.

The following knowledge management integrations are available:

Confluence

Use the Confluence integration to read wiki pages and, with approval, create or update them.

To configure the Confluence integration:

In Atlassian, generate an API token for the account that Biggy should act as.

In the web app Confluence integration page, populate the following fields:

Field	Description
Instance Name	A name to identify this Confluence instance.
Agent Notes (Optional)	Add notes to help Biggy understand your Confluence environment. We highly recommend configuring this field, as it allows you to enter organization-specific information for more accurate and consistent results.
Authentication Method	Choose how Biggy will connect to Confluence. The following options are available: Scoped API Token - API token with granular permissions routed via Atlassian's central API gateway. Recommended for Confluence Cloud. Email and API Token - Authenticate with an Atlassian account email and API token directly against your Confluence site URL.
Confluence Site URL	Enter your Confluence Cloud site URL. (For example, `https://your-domain.atlassian.net`.
Email	Enter the email address of the Atlassian account used by Biggy.
API Token	Enter the Atlassian API token generated in Step 1.
Custom Headers	Add custom HTTP headers to include with all API requests. For each header, include the Header Name and Header Value. To add additional headers, click the + sign.

Click Verify Connection to confirm that the connection to Confluence is established.

Add permission to create or update

If you want to allow Biggy to create or update Confluence pages, enable and configure the Create Knowledge Page action.

Notion

The Biggy Notion integration lets Biggy read live pages and databases from your Notion workspace. Use it to bring runbooks, service catalogs, naming conventions, and other knowledge from Notion into Biggy's investigations. With approval, you can also make governed writes back to the pages you designate.

Biggy connects to your workspace via a Notion internal integration and can see only the pages and databases you explicitly share with it. Read actions are available as soon as the connection is verified; writes remain off until an administrator enables them in the Create Knowledge Page action.

Configure the Notion integration

To configure the integration:

Log in to Notion using a workspace owner account
Navigate to Settings & members > Integrations > Develop your own integrations and create a new internal integration for Biggy.
Keep Read content on. Add Insert content and Update content only if this connection should ever write.
Share the Notion pages Biggy can see. Notion integrations see nothing by default.
On each top-level page or database, select Share, then Invite (or open the ... menu and select Connections) to add the Biggy integration. Everything nested underneath the page or database is included in the share.
Navigate to notion.so/profile/integrations and copy the internal integration secret for the Biggy integration. The secret starts with ntn_.
Paste the secret and verify the connection. In the web app Notion integration page, go to the Connection section and paste the secret into Internal Integration Secret. Click Verify Connection. The result shows which workspace and bot the secret belongs to, so you can confirm it is the right tenant before saving.
(Optional) Enable indexed search and writes. Turn on Index this workspace to make Notion content searchable alongside your other knowledge. Writes stay off until an administrator turns on Allow Biggy to write to Notion, enables individual write operations, and lists the pages or databases Biggy may write under. See Indexed search and Write access below.Indexed searchWrite access

Go to the web app Notion integration page. Populate the following fields:

Field	Description
Instance Name	A human-readable name to identify this instance.
Routing Instructions (Optional)	Describe what this instance covers so Biggy can route queries to it. (For example, `EU production accounts`) Routing instructions are recommended and are required for multiple instances.
Agent Notes (Optional)	Add notes so Biggy can find the right content. We highly recommend configuring this field, as it lets you enter organization-specific information for more accurate and consistent results. For example, note which teamspaces hold runbooks, naming conventions, and which databases track incidents or services.
Internal Integration Secret	The internal integration secret from your Notion integration, found at `notion.so/profile/integrations`. The value starts with `ntn_`. Biggy stores this value encrypted at rest and never shows it again after saving.

Under Connectivity, click Verify Connection to confirm which workspace and bot the token belongs to before you save.
(Optional) Under Indexed Search, enable Index this workspace to sync the workspace into Biggy's knowledge index, so broad questions can search Notion alongside your other sources. Live Notion reads by the agent are always current; indexed search reflects the last completed sync.
Click Re-index everything to re-read every shared page on the next cycle and remove pages that were deleted or un-shared.
(Optional) Turn on write access in the Write Access section, by enabling Allow Biggy to write to Notion. When disabled, no agent, workflow, skill, custom agent, or Swarm can create or change anything in the workspace.
To allow Biggy to create new articles, the Create Knowledge Page action must also be enabled.

In the Operation Policy section, choose which actions Biggy can perform. All Read operations are enabled by default. The following options are available:

Operation	Effect	What it does
Verify workspace identity `get_workspace_identity`	Read	Used by Verify Connection and health checks to confirm which workspace the token belongs to.
Search pages and databases by title `search`	Read	Title search across every page and database shared with the Biggy integration. The Notion API matches titles, not body text.
Read page details `get_page`	Read	Title, properties, parent, timestamps, and URL of a page by id or URL.
Read page content `get_page_content`	Read	The page body (blocks, nested content, and assets) rendered as text for the agent.
List child blocks and pages `list_block_children`	Read	Direct child blocks or child pages of a page or block.
Read database schema get_database	Read	Database title, URL, and property schema.
Query database entries `query_database`	Read	Rows of a database with bounded filters, sorts, and pagination.
Create pages `create_page`	Write	Create a new page under an allowed parent page or database. Human approval required.
Append content to pages `append_page_content`	Write	Append blocks to the end of an existing page. Human approval required.
Update page title and properties u`pdate_page_properties`	Write	Change a page title or properties without touching its body. Human approval required.

(Optional) If Write access is enabled, in Writable Destinations, choose the parent pages or databases Biggy may create under. Pages nested beneath a destination are included. The integration must already be shared with the destination in Notion.
To add a destination, paste a Notion page or database URL, or its id, and select the matching type from the Page menu, then click Add destination.
If Write access is enabled, use the Which existing pages may be updated menu to control which pages can be updated. Select one of the following options:
1. Only pages under a writable destination (recommended): Append and retitle are refused for pages outside the destinations listed above. If no destinations are defined, every update is refused.
2. Any page shared with Biggy: Biggy can update any page that was shared with it.

In this section:

Knowledge Management Integrations

Confluence

Notion

Configure the Notion integration

Search results