Notion

Query databases, create pages, and manage blocks with the Notion API.

Detail	Value
Category	Productivity
Base URL	https://api.notion.com
Authentication	Bearer Token
Endpoints	6
Connector key	notion

Using Notion in a workflow

1. Go to Connections and click New Connection.
2. Pick Notion from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
POST /databases/{database_id}/query	Query a database
POST /pages	Create a page
GET /pages/{page_id}	Retrieve a page
PATCH /pages/{page_id}	Update page properties
GET /blocks/{block_id}/children	Get block children
POST /search	Search pages and databases

Each endpoint is documented in full below. Use the outline on the right to jump to one.

POST /databases/{database_id}/query

Query a database

Detail	Value
Operation ID	data.queryDatabase
Method	POST
Path	/databases/{database_id}/query

Parameters

Name	Location	Type	Required
database_id	path	string	Yes

Request Body

Field	Type
filter	object
sorts	array

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Notion connection from the Connection dropdown.
3. In the Operation dropdown, select data.queryDatabase.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Notion API reference.

POST /pages

Create a page

Detail	Value
Operation ID	data.createPage
Method	POST
Path	/pages

Parameters

No parameters.

Request Body

Field	Type
parent	object
properties	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Notion connection from the Connection dropdown.
3. In the Operation dropdown, select data.createPage.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Notion API reference.

GET /pages/{page_id}

Retrieve a page

Detail	Value
Operation ID	data.getPage
Method	GET
Path	/pages/{page_id}

Parameters

Name	Location	Type	Required
page_id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Notion connection from the Connection dropdown.
3. In the Operation dropdown, select data.getPage.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Notion API reference.

PATCH /pages/{page_id}

Update page properties

Detail	Value
Operation ID	data.updatePage
Method	PATCH
Path	/pages/{page_id}

Parameters

Name	Location	Type	Required
page_id	path	string	Yes

Request Body

Field	Type
properties	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Notion connection from the Connection dropdown.
3. In the Operation dropdown, select data.updatePage.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Notion API reference.

GET /blocks/{block_id}/children

Get block children

Detail	Value
Operation ID	data.getBlockChildren
Method	GET
Path	/blocks/{block_id}/children

Parameters

Name	Location	Type	Required
block_id	path	string	Yes

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Notion connection from the Connection dropdown.
3. In the Operation dropdown, select data.getBlockChildren.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Notion API reference.

POST /search

Search pages and databases

Detail	Value
Operation ID	data.search
Method	POST
Path	/search

Parameters

No parameters.

Request Body

Field	Type
query	string
filter	object

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Notion connection from the Connection dropdown.
3. In the Operation dropdown, select data.search.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked — fill them or the call will fail at runtime.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Notion API reference.