Actions16
Overview
The node provides advanced integration with a popular note-taking and productivity platform, enabling users to perform various operations on its resources such as pages, blocks, databases, and users. Specifically for the Database - Create operation, it allows creating a new database within a specified parent page. This is useful for automating the setup of structured data repositories in the platform, such as project trackers, inventories, or content catalogs.
Practical examples include:
- Automatically creating a new project database with predefined properties when a new project is initiated.
- Setting up client databases dynamically based on incoming CRM data.
- Generating custom databases for event management or content planning workflows.
Properties
| Name | Meaning |
|---|---|
| Parent | The ID of the parent page under which the new database will be created. |
| Title | The title of the new database. |
| Properties | A collection of property definitions for the database. Each property includes: |
| - Name: The name of the property. | |
| - Type: The type of the property (e.g., title, rich text, number, select, multi-select). | |
| - Value: The value or configuration for the property, provided as JSON for complex types. | |
| Additional Fields | Not applicable for this operation (present in other resource operations). |
Output
The output is a JSON object representing the newly created database as returned by the platform's API. It includes details such as:
- Database ID
- Parent page information
- Title (as rich text)
- Defined properties with their types and configurations
This output can be used downstream in workflows to reference the created database or extract metadata.
Dependencies
- Requires an active connection using valid API credentials for the target platform.
- The node depends on internal utility functions for:
- Resolving page IDs from input strings.
- Creating rich text objects for titles.
- Making authenticated HTTP requests to the platform's API endpoints.
- No additional external services are required beyond the platform's official API.
Troubleshooting
- Invalid Credentials Error: If the node throws an error about invalid API credentials, verify that the API key or token is correctly configured and has sufficient permissions to create databases.
- Invalid Property JSON: When defining properties, ensure that the "Value" field contains valid JSON if the property type requires complex configuration. Malformed JSON will cause errors.
- Parent Page Not Found: The parent page ID must be valid and accessible. Errors may occur if the parent does not exist or the user lacks access rights.
- API Rate Limits: Frequent creation requests might hit API rate limits; consider adding delays or error handling for retries.