Skip to main content
Notion logo

Notion

Overview

Notion is a versatile all-in-one workspace that empowers teams to collaborate and organize seamlessly. Integrate Notion with Superblocks to effortlessly synchronize data, automate tasks, and visualize your Notion data in Superblocks.

Setting up Notion

Create an access token

To get started you'll need a Notion access token. To create a token:

  1. Log in to Notion
  2. Go to your Integrations page
  3. Click Create new integration or choose an existing one
  4. Copy the integration's access token
  5. Share a database with your integration
  6. Use your access token to configure your integration's connection

Learn more about Notion API Authentication

Add integration

Once you have an access token, you're ready to set up your Superblocks integration.

  1. In the web app, navigate to the Integrations page
  2. Click on the Notion tile
  3. Name the integration
  4. Paste your credentials into the relevant fields
  5. Optionally, add more configurations to set credentials for different environments
  6. Click Create
tip

Notion connected!
Now you can use Notion in any Application, Workflow, or Scheduled Job.

Use Notion in APIs

Once your Notion integration is created, you can start calling Notion actions in Superblocks APIs.

Notion actions are REST requests. To learn more about REST requests in Superblocks, see the Building REST requests guide.

Supported actions

Search

Search

Create a database

Create a database and its initial data source. Creates a database as a subpage in the specified parent page, or as a private page at the workspace level, with the specified properties schema set on its initial_data_source. The parent of a new database must be a Notion page (page_id type) or a wiki database.

Retrieve a database

Retrieves a database object — a container for one or more data sources — for a provided database ID. The most important fields in the database object response: - data_sources: An array of JSON objects with the id and name of every data source under the database - parent: The direct parent of the database; generally a page_id or workspace: true

Update a database

Updates the attributes — the title, description, icon, or cover, etc. — of a specified database. Returns the updated database object. To update the properties of the data sources under a database, use the Update a data source API starting from API version 2025-09-03.

Create a data source

Use this API to add an additional data source to an existing database. The properties follow the same structure as the initial schema passed to initial_data_source[properties] in the Create a database API, but can be managed independently of the properties of any sibling data sources. A standard "table" view is created alongside the new data source. To customize database views, use the Notion app. Managing views is not currently supported in the API.

Retrieve a data source

Retrieves a data source object — information that describes the structure and columns of a data source — for a provided data source ID. The response adheres to any limits to an integration's capabilities and the permissions of the parent database. To fetch data source rows (i.e. the child pages of a data source) rather than columns, use the Query a data source endpoint. Note: Data source relations must be shared with your integration. To retrieve data source properties from database relations, the related database must be shared with your integration in addition to the database being retrieved.

Update a data source

Updates the data source object — the properties, title, description, or whether it's in the trash — of a specified data source under a database. Returns the updated data source object. Use the parent parameter to move the data source to a different database_id. If you do so, any existing views that refer to the data source in the current database continue to exist, but become linked views. Data source properties represent the columns (or schema) of a data source. To update the properties of a data source, use the properties body param with this endpoint. Note: The following data source properties cannot be updated via the API: formula, status, synced content, place.

Query a data source

Gets a list of pages contained in the data source, filtered and ordered according to the filter conditions and sort criteria provided in the request. The response may contain fewer than `page_size` of results. If the response includes a `next_cursor` value, refer to the pagination reference for details about how to use a cursor to iterate through the list. Filters operate on data source properties and can be combined. If no filter is provided, all the pages in the data source will be returned with pagination. Sorts operate on database properties or page timestamps and can be combined. The order of the sorts in the request matter, with earlier sorts taking precedence over later ones. Use the `filter_properties` query parameter to filter only the properties you need from the response to improve API performance. Note: Before an integration can query a data source, its parent database must be shared with the integration.

List data source templates

Retrieves details of all page templates available for a data source. The response contains an array of template objects under the `templates` key. Each template has: - `id`: The ID of the template (UUIDv4) - `name`: The display name of the template - `is_default`: Whether that template is the data source's default Only templates under the data source identified by `data_source_id` are returned. The bot must have access to the template for it to appear. In most cases, as long as the bot is connected to the data source's parent database, this access extends to all child templates. Templates are also valid Notion pages, so you can retrieve a template's full properties and content using the Retrieve a page API.

Create a page with content

Create a page with content

Retrieve a page

Retrieves a Page object using the ID in the request path. This endpoint exposes page properties, not page content.

Update page properties

Updates a page by setting the values of any properties specified in the JSON body of the request. Properties not updated via parameters will remain unchanged.

Retrieve a page property item

Retrieve a page property item

Retrieve comments

Retrieve a user object using the ID specified in the request path.

Add comment to discussion

Add comment to discussion

Retrieve a block

Retrieves a Block object using the ID specified. If the block returned contains the key `has_children: true`, use the Retrieve block children endpoint to get the list of children. To retrieve page content for a specific page, use Retrieve block children and set the page ID as the `block_id`. Note: This endpoint requires an integration to have read content capabilities.

Update a block

This endpoint allows you to update block content. [See Full Documentation](https://developers.notion.com/reference/update-a-block)

Delete a block

Delete a block

Retrieve block children

Returns a paginated array of child block objects contained in the block using the ID specified. In order to receive a complete representation of a block, you may need to recursively retrieve the block children of child blocks. Page content is represented by block children. Returns only the first level of children for the specified block. See block objects for more detail on determining if that block has nested children. The response may contain fewer than `page_size` of results. Note: This endpoint requires an integration to have read content capabilities.

Append block children

Append block children

List all users

Returns a paginated list of user objects for a workspace

Retrieve a user

Retrieve a user object using the ID specified in the request path.
and 7 more

Generic HTTP Request

Every SaaS integration in Superblocks comes with a built in Generic HTTP Request Action. This is a powerful action you can use to call Notion API endpoints not in the Superblocks supported actions.

To use this action simply add the method, path, required query parameters, and body for the desired endpoint.

info

Learn more about REST requests in Superblocks in our Building REST requests guide.

Generic HTTP Requests use the authentication set up and base URL you've configured for your integration, making it an easy for your team to extend Superblocks Integrations to meet their needs.