Integrate Notion Notifications
Overview
You can integrate Notion notifications to automatically record file transfer events in a Notion database.
Once the integration is complete, a new record is automatically added to the specified Notion database whenever selected events occur, such as Started, Completed, or Failed.
The setup consists of three steps:
① Create a Notion Integration and obtain an Internal Integration Token → ② Connect the Integration and obtain the Database ID → ③ Configure notification settings in the product
Prerequisites
Before you begin, verify the following requirements.
| Item | Description |
|---|---|
| Notion Workspace | An account with permission to create Integrations is required. |
| Target Database | Prepare the Notion database where notification records will be stored. |
| Network | The environment where the product is installed must allow outbound HTTPS (443) access to api.notion.com. |
Create a Notion Integration and Obtain an Internal Integration Token
To send notifications to Notion, first create a Notion Integration and obtain its Internal Integration Token.
Step 1. Create an Integration
Open https://www.notion.so/my-integrations and click + New integration.
Alternatively, you can access the same page from Settings → Connections in Notion.
Select Internal as the integration type, enter a name (for example, `INNORIX CONNECTION), and choose the workspace where the integration will be created.

Step 2. Configure Capabilities
Enable at least the following permissions before saving the integration:
- Read content
- Insert content
These permissions allow the integration to create new records in your database.

Step 3. Copy the Internal Integration Token
Copy the Internal Integration Token. The token begins with ntn_.
This token is a sensitive credential. Anyone with this token can access the connected data according to the granted permissions, so do not expose it in public repositories or external documents.
If the token is compromised, you can generate a new one by refreshing it in the Integration settings.

Verification
- ✔ The Internal Integration has been created.
- ✔ The required permissions have been enabled.
- ✔ The Internal Integration Token has been copied.
Connect the Database and Obtain the Database ID
Creating an Integration alone does not grant access to your database.
You must connect the Integration to the target database and then obtain the Database ID.
Step 1. Connect the Integration to the Database
Open the target Notion database as a full page.
From the ••• menu in the upper-right corner, select Add connections, then search for and select the Integration created in the "Create a Notion Integration" section.

Step 2. Obtain the Database ID
Open the database as a full page and check the URL in your browser.
The 32-character string located between the workspace name and ?v= is the Database ID.
The Database ID must belong to the original database.
Do not use the ID of an inline database or a linked database view.
If the URL contains ?v=, it is a database view. Entering a regular page ID instead of the database ID will cause the connection to fail.

Verification
- ✔ The Integration has been connected to the target database.
- ✔ The Database ID has been copied.
Configure Notion Notifications
Enter the Internal Integration Token and Database ID into the product notification settings.
Open the Notifications settings page.

Step 1. Enter the Internal Integration Token
Paste the token copied in the "Create a Notion Integration" section into the Internal Integration Token field.
Step 2. Enter the Database ID
Paste the Database ID obtained in the "Connect the Database and Obtain the Database ID" section into the Database ID field.
Step 3. Select Notification Events
Select the events that should create records in the Notion database.
You can select multiple events. A new database record is created only when one of the selected events occurs.
| Event | Trigger |
|---|---|
| Started | When a file transfer starts |
| Completed | When a file transfer completes successfully |
| Paused | When a transfer is paused |
| Resumed | When a paused transfer resumes |
| Recovered | When a transfer automatically recovers after an interruption or error |
| Canceled | When a transfer is canceled by the user |
| Failed | When a transfer fails |
| Skipped | When a file is skipped (for example, because it already exists or matches a filter rule) |
Step 4. Save the Configuration
Click Add to save the integration.
Verification
- ✔ The Internal Integration Token has been entered.
- ✔ The Database ID has been entered.
- ✔ The notification events have been selected.
Verify the Integration
Verify that the integration is working correctly.
Step 1. Trigger a Test Event
Start an actual file transfer or trigger one of the selected notification events.

Step 2. Check the Notion Database
Confirm that a new notification record has been created in the configured Notion database.

Verification
- ✔ A new notification record has been added to the database.
- ✔ The event information has been recorded correctly.
Configuration Complete
Once the configuration is saved, the integration becomes active.
From this point forward, a new notification record is automatically created in the configured Notion database whenever one of the selected events occurs.
Troubleshooting
If notification records are not created, verify the following items.
| Issue | Check |
|---|---|
| No record is created | Verify that the Internal Integration Token and Database ID are entered correctly and contain no extra spaces or missing characters. |
| Permission error | Confirm that the Integration has been connected to the target database (••• → Add connections) and that the Insert content capability is enabled. |
| Database cannot be found | Verify that the Database ID belongs to the original database (the URL containing ?v=). Regular page IDs or linked database view IDs cannot be used. |
| Record creation fails because of property errors | Confirm that the required database properties exist and are configured correctly. |
| Notification delivery fails in a restricted network | Ensure that outbound HTTPS (443) access to api.notion.com is allowed through the firewall or proxy. |