Notion integration

Updated 1 week ago by Fazila Malik

Notion is a content collaboration tool used to help teams collaborate and share knowledge efficiently. With atSpoke, you can access resources from Notion to atSpoke's knowledge base.

Interested in learning more about atSpoke to improve your internal employee support? Book a demo here.

Access to the Notion integration is available to Team, Business, and Enterprise plans

Video Tutorial

Setup

  1. Navigate to Settings
  2. Select the Integrations tab
  3. Scroll through the menu until you reach the Knowledge Management section, then choose Notion
Only Super Admins can view, enable, configure, edit, and disable Integrations
  1. You'll be directed to your Notion instance to complete the Oauth.
  2. Select Pages to open the list of pages and click on the Notion pages you would like to map in atSpoke and select Allow access.

Edit Connection

  1. Navigate to Settings
  2. Choose the Integrations Menu
  3. Click on the Notion card choose Edit Connection
  4. Map your atSpoke team to a Notion page.
  5. Click "Update connection" when your atSpoke team has the appropriate Notion page.

Knowledge base resources

Navigate to the Knowledge section in the sidenav where you can begin to add Notion resources. Click the arrow button and click the Notion icon add resources.

  1. Navigate to Knowledge in the side nav
  2. Click the downward arrow next to Add Resource
  3. Select the Notion icon
  4. In the next window sync your Notion articles to each team. Select the articles you's like to import.
  5. File the resource under the appropriate atSpoke team
  6. Click "Import"

These resources will passively sync with your Notion pages where any edit or change in your Notion portal will be reflected in your atSpoke import.

Syncing resources

Once you've imported your resource from Notion, they will sync daily. This means that if the title of the Notion resource changes, you will see the change reflected in the atSpoke knowledge base resource.

If atSpoke has been trained on a resource that was then renamed, it might take a few days to retrain the updated resource


How did we do?


Powered by HelpDocs (opens in a new tab)