Skip to main content

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.Actions

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:

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

  2. 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. 

  3. 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. Actions

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.Actions

Configure the Notion integration

To configure the integration:

  1. Log in to Notion using a workspace owner account 

  2. 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.

  3. 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.

  4. Navigate to notion.so/profile/integrations and copy the internal integration secret for the Biggy integration. The secret starts with ntn_.

  5.  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.

  6. (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

  7. 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.

  8. Under Connectivity, click Verify Connection to confirm which workspace and bot the token belongs to before you save.

  9. (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.

  10. (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.Actions

  11. 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 update_page_properties

    Write

    Change a page title or properties without touching its body. Human approval required.

  12. (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.

  13. 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.

SharePoint

The Biggy SharePoint integration lets Biggy read live pages and documents from SharePoint Online. Use it to bring runbooks, postmortems, service documentation, and other knowledge from SharePoint into Biggy's investigations. You can also grant  approval-gated page writes back to the sites you designate.

Biggy connects to your tenant through a Microsoft Entra app registration that uses Microsoft Graph application permissions. Biggy reads only the sites you list on the integration, and writes only to sites marked Allow writes. Writes happen only after a person has approved each one, through the Create Knowledge Page and Update Knowledge Page actions.

Microsoft Graph permissions

The SharePoint integration uses the following Microsoft Graph application permissions. All application permissions require admin consent.

Permission

Required

Description

Sites.Selected

Recommended

Gives per-site access. Biggy sees only the sites that a SharePoint admin grants to the app, one site at a time. Grant each site Read access, or Write access for sites where Biggy may create or update pages.

Sites.Read.All

Optional

Lets Biggy search through the Microsoft Search index instead of site by site. Results and reads stay limited to the sites listed on the integration.

Sites.ReadWrite.All

Optional

Allows page writes across the tenant. Not required with Sites.Selected, because a Write grant on the site is enough. Writes stay limited to sites marked Allow writes, regardless of what this permission allows.

Use per-site access

We recommend using Sites.Selected with per-site grants. This limits Biggy to the specific sites your team approves, rather than every site in the tenant.

Configure the SharePoint integration

To configure the integration:

  1. Register an app for Biggy in Microsoft Entra.

    In the Microsoft Entra admin center, open App registrations > New registration. 

  2. Name the app Biggy, keep Accounts in this organizational directory only selected, and click Register.

  3. On the app registration's Overview page, copy the Directory (tenant) ID and the Application (client) ID. You will paste these values into BigPanda in a later step.

  4. Add Microsoft Graph application permissions.

    Go to API permissions > Add a permission > Microsoft Graph > Application permissions and add Sites.Selected.

    (Optional) Add Sites.Read.All so Biggy can search through the Microsoft Search index instead of site by site. Results stay limited to the sites you list on the integration.

  5. Grant admin consent. A Global Administrator or Privileged Role Administrator must select Grant admin consent for the app's permissions.

  6. Grant the app access to each site. Sites.Selected grants no access until a SharePoint admin grants each site individually. Use one of the following methods:

    •  PnP PowerShell: Run the following:

      Grant-PnPAzureADAppSitePermission -Site  -AppId  -DisplayName Biggy -Permissions Read

       In PnP PowerShell 2.x, use Grant-PnPEntraIDAppSitePermission instead. For sites Biggy may write to, use -Permissions Write.

    •  Graph Explorer: Send POST /sites/<site_id>/permissions with the app and the read or write role.

  7. Open Certificates & secrets, then select New client secret. Copy the secret value.

    Copy secret value

    Copy the secret value, not the secret ID.

    Client secrets expire

    Microsoft Entra client secrets have an expiration date. Rotate the secret in the app registration and update it in BigPanda before it expires to avoid losing the connection.

  8. Grant the app access to each site. Sites.Selected grants no access until a SharePoint admin grants each site individually. Use one of the following methods:

    •  PnP PowerShell: Run Grant-PnPAzureADAppSitePermission -Site <site_url> -AppId <client_id> -DisplayName Biggy -Permissions Read. In PnP PowerShell 2.x, use Grant-PnPEntraIDAppSitePermission instead. For sites Biggy may write to, use -Permissions Write.

    •  Graph Explorer: Send POST /sites/<site_id>/permissions with the app and the read or write role.

  9. In the web app SharePoint integration page, populate the following fields:

    Field

    Description

    Instance Name

    A human-readable name to identify this instance. For example, Production SharePoint.

    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 sites hold runbooks or postmortems, page naming conventions, and which libraries track services.

    Directory (tenant) ID

    The Directory (tenant) ID from the app registration's Overview page in Microsoft Entra ID. The value uses the format 00000000-0000-0000-0000-000000000000.

    Application (client) ID

    The Application (client) ID of the app registration you created for Biggy.

    Client Secret

    The client secret value. Biggy stores this value encrypted at rest. Client secrets expire, so rotate them in the app registration before they do.

    Microsoft cloud

    Select the Microsoft cloud your tenant uses. This setting selects the Microsoft Entra sign-in and Microsoft Graph endpoints. Commercial and GCC tenants use the global cloud, Microsoft 365 (global, default; also GCC).

  10. Under Connectivity, click Verify Connection to confirm that the connection to SharePoint is established.

  11. In the Sites section, add each site you granted to the app. Paste the site address into the site field, then click Add site. For example, https://<tenant>.sharepoint.com/sites/Operations.

    You can add the tenant root, a /sites/ site, or a /teams/ site. Page, library, and OneDrive links are not sites and aren't accepted. Biggy reads only the sites listed here.

  12. (Optional) Turn on Allow writes for each site where Biggy may create or update pages, such as sites that hold runbooks or postmortems. Page writes also require a write grant on that site, or the Sites.ReadWrite.All permission.

    To allow Biggy to create new pages, the Create Knowledge Page action must also be enabled.

    Read-only connection

    If no site has Allow writes turned on, the connection is read-only and BigPanda blocks every page write server-side.

  13. If write access is enabled, use the Which existing pages may be updated menu to control which existing pages Biggy can update. Select one of the following options:

    •  Only pages in sites marked Allow writes: Biggy can update an existing page only when it lives in a listed site with Allow writes turned on.

    • Any page Biggy can read: Biggy may update any existing page the Entra app can write to. New pages still go only to sites with Allow writes on.

  14. Click Create Instance.