Overview#
You can integrate Notion notifications to automatically record status changes during file transfer tasks in Notion.
After completing the integration, a notification entry is automatically added to the designated Notion database whenever designated events occur, such as a transfer being Started, Completed, or Failed.
The entire process proceeds in the following order: ① Create a Notion integration and obtain a token → ② Connect the database and check the Database ID → ③ Configure notifications in the product.
Prerequisites#
Before you begin, check the following.
| Item | Description |
|---|---|
| Notion workspace | An account with permission to create integrations (Integration) is required. |
| Target database | Prepare the Notion database where notifications will be recorded in advance. |
| Network | Outbound HTTPS communication to api.notion.com (443) must be allowed from the environment where the product is installed. |
Create a Notion Integration and Obtain a Token#
To receive notifications in Notion, first create a Notion integration (Integration) and use the issued token.
Step 1. Create an Integration#
Go to https://www.notion.so/my-integrations and select + New integration.
Alternatively, you can also access it from the Connections menu in Notion settings.
Keep the integration type as Internal, enter a name (Example: INNORIX CONNECTION), and select the workspace to connect.
Step 2. Configure Permissions (Capabilities)#
To add notification entries to the database, enable at least Read content and Insert content permissions, then save the settings.
Step 3. Copy the Token#
Copy the Internal Integration Token (internal integration secret). The token starts with ntn_.
ℹ️ This token is sensitive information, similar to a password. Anyone who knows the value can access the connected data, so make sure it is not exposed in public repositories or external documents. If the token is exposed, you can issue a new one (Refresh) in the Integration settings.
Checklist#
- ✔ The internal integration has been created.
- ✔ The required permissions have been configured.
- ✔ The Internal Integration Token has been copied.
Connect the Database and Check the Database ID#
An integration cannot access a database simply by being created.
After connecting the integration to the database where notifications will be recorded, check the Database ID.
Step 1. Connect the Integration to the Database#
Open the Notion database where notifications will be recorded as a full page.
From the ••• menu in the upper-right corner, select Add connections, then search for and connect the Integration created during integration setup.
Step 2. Check the Database ID#
With the database open as a full page, check the URL in the browser address bar.
The 32-character string between / and ?v= after the workspace name is the Database ID.
https://app.notion.com/p/3b45f9584aaa8018b99ed8a0c558ba2c?v=...
└──────── Database ID ────────┘The Database ID must be the ID of the original database.
You cannot use the ID of an inline database or a linked database view.
If the URL contains ?v=, it represents a database view, and entering a regular page ID will cause the connection to fail.
Checklist#
- ✔ The integration has been connected to the target database.
- ✔ The Database ID has been copied.
Notion Notification Settings#
Enter the issued token and Database ID in the product's notification settings.
When you open the Notifications settings window, the following screen is displayed.
Step 1. Enter the Internal Integration Token#
Paste the token copied during integration setup into the Internal Integration Token field.
Step 2. Enter the Database ID#
Paste the confirmed Database ID into the Database ID field.
Step 3. Select Notification Events#
Select the events for which you want to receive notifications under Events.
You can select multiple events, and a new entry is added to the database only when the selected events occur.
| Event | When It Occurs |
|---|---|
| Started | When the transfer task starts |
| Completed | When the transfer is completed successfully |
| Paused | When the transfer is temporarily paused |
| Resumed | When a paused transfer starts again |
| Recovered | When the transfer is automatically recovered and resumed after an interruption or error |
| Canceled | When the user cancels the transfer |
| Failed | When the transfer fails |
| Skipped | When a specific file is skipped (Example: an existing file or a file matching a filter condition) |
Step 4. Save the Settings#
After completing the input, click Add to save the integration.
Checklist#
- ✔ The Internal Integration Token has been entered.
- ✔ The Database ID has been entered.
- ✔ The events for which notifications will be received have been selected.
Verify the Integration#
Verify that the settings are working correctly.
Step 1. Trigger a Test Event#
Run an actual transfer task or trigger one of the selected events.
Step 2. Check the Notion Database#
Check whether a new notification entry has been created in the designated Notion database.
Checklist#
- ✔ A notification entry has been added to the database.
- ✔ The triggered event was recorded accurately.
Setup Complete#
Once the settings are saved, the integration is applied.
After that, a notification entry is automatically added to the designated Notion database whenever the selected events occur.
Troubleshooting#
If notification entries are not created, check the following items.
| Issue | What to Check |
|---|---|
| An entry is not created | Check whether the Internal Integration Token and Database ID were entered correctly (including leading or trailing spaces and missing characters). |
| A permission error occurs | Check whether the Integration is connected to the target database (••• → Add connections) and whether the Insert content permission is enabled. |
| The database cannot be found | Check whether the Database ID is the ID of the original database (with ?v= in the URL). You cannot use the ID of a regular page or a linked database view. |
| Creation fails due to a property-related error | Check whether the required database properties for storing notifications are configured. |
| Notification failure in a closed network | Check whether outbound HTTPS communication to api.notion.com (443) is allowed by the firewall or proxy. |