Database Items

Data

Databases

Pages

Users

Notion

Get Markdown from page

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

Retrieve a user

Returns a paginated list of user objects for a workspace

List all users

Retrieve bot's user info

Retrieves a database object using the ID specified in the request path. 

Retrieve a database

Update a database

Query a database

Create a database

Create a Page with Content

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

Retrieve a Page

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.

Update Page properties 

Delete a block

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

Update a block

Retrieve a block

Retrieve a Page Property Item

Retrieve block children

Append block children

Search

Retrieve comments

Add comment to discussion

Microsoft Sharepoint

Salesforce

HubSpot

Microsoft Dynamics 365

Zoho CRM

Pipedrive

Monday

Freshsales

Slack

Keap

Jira

SugarCRM

Asana

Outreach

Xero

ActiveCampaign

Capsule CRM

Github

Salesloft

Clickup

Agile CRM

SalesForce Pardot

SharpSpring

Teamleader

Insightly

Zendesk

Attio

Copper

Microsoft Teams

Greenhouse Harvest

Zoho Books

Front

Calendly

Close

Freshdesk

BambooHR

Breezy HR

Basecamp

Okta

Deel

Lever

Google Workspace

Microsoft Entra ID

# Continuous Import of Users to Your App

This scenario enables your application to continuously sync Users from any external application to your app's API. It handles the initial import of Users and keeps them synchronized when a User is created, updated, or deleted in the external application.

When receiving Users data from the external application, the data is transformed into a format supported by your app's API. Additionally, if needed, your customers can customize the data mapping based on their specific external application setup.

## How It Works

1. **Initial Import**:
   - Perform the initial import by calling the Integration.app REST API or SDK in a loop from your code to retrieve data page by page.
   - Integration.app transforms the output into a consistent format compatible with your API, allowing you to save the data efficiently.

2. **Continuous Sync**:
   - Enable subscription via a single API or SDK call to continuously receive created, updated, or deleted events.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.

Continuously Import Users to my App

Import Users and receive created/updated or deleted events

Confluence

# Delete Document

This scenario allows your application to delete a Document from any external application. 
You will pass ID of the Document you want to delete and Integration.app will handle the rest.

## How It Works

1. **Delete Document API call**:
   - Call Integration.app REST API or SDK with ID of the Document you want to delete and Integration.app will send the correct request to the external app.


Delete Document

Deletes Document in any external application

Google Docs

# Create Document

This scenario allows your application to create a Document in any external application in the same way. 
You will pass Document fields in any format your application support and Integration.app will handle mapping of them to the schema of any selected application.
Additionally, if needed, your customers can customize the data mapping based on their specific setup.


## How It Works

1. **Configuration**:
   - You will setup the schema of fields that you wish to create Document with and configure mapping to our default model

2. **Create Document API call**:
   - Call Integration.app REST API or SDK with payload matching the field mapping you configured. You can run it for any external application via the same request.
   - When called, Integration.app transforms your Document data into a format compatible with the selected external application.
   - It then makes an API call to create the Document in that specific application.


Create Document

Creates Document in any external application

# Realtime Full two-way Sync of Documents

This scenario enables your application to fully sync Documents between your app and any external application in both directions. It handles the initial import/export of Documents and then sends events when a Document is created, updated, or deleted on any side, as close to real-time as possible.

Document fields will be mapped from your application's schema to the application-specific schema.

## How It Works

1. **Initial Sync**:
   - Perform the initial import by calling the Integration.app REST API or SDK in a loop from your code to retrieve data page by page. Integration.app transforms the output into a consistent format compatible with your API, allowing you to save and match data efficiently.
   - Make another set of requests to create Documents in external app, if needed.

2. **Continuous Sync from External App**:
   - Enable subscription via a single API or SDK call to continuously receive created, updated, or deleted events from external applications.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.


2. **Continuous Sync from Your App**:
   - You will get a single webhook URI that you will use to send events about created, updated, or deleted Documents to Integration.app.
   - Once send, Integration.app will map the webhook payload to the format supported by external application and send the correct request


Two-way realtime sync of Documents

Bi-directional realtime sync of Documents with records deduplication

# Continuous Import of Documents to Your App

This scenario enables your application to continuously sync Documents from any external application to your app's API. It handles the initial import of Documents and keeps them synchronized when a document is created, updated, or deleted in the external application.

When receiving Documents data from the external application, the data is transformed into a format supported by your app's API. Additionally, if needed, your customers can customize the data mapping based on their specific external application setup.

## How It Works

1. **Initial Import**:
   - Perform the initial import by calling the Integration.app REST API or SDK in a loop from your code to retrieve data page by page.
   - Integration.app transforms the output into a consistent format compatible with your API, allowing you to save the data efficiently.

2. **Continuous Sync**:
   - Enable subscription via a single API or SDK call to continuously receive created, updated, or deleted events.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.

Continuously Import Documents to my App

Import Documents, download Documents content and receive created/updated or deleted events

# Get all Documents

This scenario enables your application to get a complete list of Documents from any external application to your app's API in the same way. 

When receiving Documents data from the external application, the data is transformed into a format supported by your app's API. Additionally, if needed, your customers can customize the data mapping based on their specific external application setup.

## How It Works

You will call a Integration.app REST API endpoint or SDK methods to retrieve a single page of Documents along with the `cursor` if next page is available.
Repeate this request in a loop from your code to retrieve all Documents page by page.


Get all Documents

Imports all Documents from any external application to your App.

# Update Document

This scenario allows your application to update a Document in any external application in the same way. 
You will pass  ID of the Document you want to update and Document fields in any format your application support and Integration.app will handle mapping of them to the schema of any selected application.
Additionally, if needed, your customers can customize the data mapping based on their specific setup.

## How It Works

1. **Configuration**:
   - You will setup the schema of fields that you wish to update Document with and configure mapping to our default model

2. **Create Document API call**:
   - Call Integration.app REST API or SDK with payload matching the field mapping you configured and ID. You can run it for any external application via the same request.
   - When called, Integration.app transforms your Document data into a format compatible with the selected external application.
   - It then makes an API call to update the Document in that specific application.


Update Document

Updates Document in any external application

# Get all Users

This scenario enables your application to get a complete list of Users from any external application to your app's API in the same way. 

When receiving Users data from the external application, the data is transformed into a format supported by your app's API. Additionally, if needed, your customers can customize the data mapping based on their specific external application setup.

## How It Works

You will call a Integration.app REST API endpoint or SDK methods to retrieve a single page of Users along with the `cursor` if next page is available.
Repeate this request in a loop from your code to retrieve all Users page by page.


Get all Users

Imports all Users from any external application to your App.

# Realtime Full two-way Sync of Users

This scenario enables your application to fully sync Users between your app and any external application in both directions. It handles the initial import/export of Users and then sends events when a User is created, updated, or deleted on any side, as close to real-time as possible.

User fields will be mapped from your application's schema to the application-specific schema.

## How It Works

1. **Initial Sync**:
   - Perform the initial import by calling the Integration.app REST API or SDK in a loop from your code to retrieve data page by page. Integration.app transforms the output into a consistent format compatible with your API, allowing you to save and match data efficiently.
   - Make another set of requests to create Users in external app, if needed.

2. **Continuous Sync from External App**:
   - Enable subscription via a single API or SDK call to continuously receive created, updated, or deleted events from external applications.
   - Integration.app manages all integration-specific logic, including subscribing to/unsubscribing from webhooks, custom polling of events, or performing periodic full syncs.
   - You will only receive the necessary events as real-time as supported by the external application's API.


2. **Continuous Sync from Your App**:
   - You will get a single webhook URI that you will use to send events about created, updated, or deleted Users to Integration.app.
   - Once send, Integration.app will map the webhook payload to the format supported by external application and send the correct request


Two-way realtime sync of Users

Bi-directional realtime sync of Users with records deduplication

# User Unified API

This scenario contains the complete Users Unified API into your workspace. You will be able to seamlessly create, update, delete, and search Users while also receiving notifications on creation, updates, and deletions of Users in external applications. 

Integration.app will automatically manage the mapping of data to the unified schema, eliminating any concerns about differences across external applications. Additionally, you’ll have the flexibility to customize mappings for specific applications or customers, ensuring compatibility with their unique configurations when needed.


Field Name	API Key	Type
Path Parameters	pathParameters	object
Id	pathParameters.id	string
Query	query	object
Data	data	object
Title	data.title	array of items

Field Name	API Key	Type
Object	object	string
Id	id	string
Created Time	created_time	string
Created By	created_by	object
Object	created_by.object	string

Notion API Integration Profile

Update a database in Notion API

Build every single integration your customers need with AI