Short answer: Drop the "Notion → Create Database" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Parent Page ID parent_page_id | string | Required | The ID of the page that will contain the new database |
Database Title title | string | Required | Title for the new database |
Properties (JSON) properties | string | Optional | Database property schema as JSON. Defines the columns. A title property is always included automatically. |
{"parent_page_id": "e.g. a1b2c3d4-e5f6-7890-abcd-ef1234567890","title": "e.g. Project Tasks","properties": "{\"Status\": {\"select\": {\"options\": [{\"name\": \"To Do\"}, {\"name\": \"Done\"}]}}, \"Assignee\": {\"rich_text\": {}}}"}
{"id": "db-new-id-123","url": "https://www.notion.so/Database-abc123","title": [{"plain_text": "Project Tasks"}],"object": "database","properties": {"Name": {"id": "title","type": "title","title": {}},"Status": {"id": "abc","type": "select","select": {"options": [{"name": "To Do","color": "red"},{"name": "Done","color": "green"}]}}},"created_time": "2025-01-15T12:00:00.000Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.