Short answer: Drop the "Notion → Query 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 |
|---|---|---|---|
Database ID database_id | string | Required | Notion database ID — a UUID with hyphens. Open the database as a full page, copy the URL, format as 8-4-4-4-12 hex. |
Filter (JSON) filter | string | Optional | Notion filter object as JSON. See Notion API docs for filter syntax. |
Sort By Property sort_property | string | Optional | Name of the property to sort by |
Sort Direction sort_direction | options | Optional | Sort Direction. Options: Descending, Ascending |
Page Size page_size | string | Optional | Number of rows to return (max 100) |
{"database_id": "e.g. a1b2c3d4e5f6...","filter": "{\"property\": \"Status\", \"select\": {\"equals\": \"Done\"}}","sort_property": "e.g. Created time","sort_direction": "{{trigger.sort_direction}}","page_size": "100"}
{"object": "list","results": [{"id": "row-id-123","object": "page","properties": {"Name": {"title": [{"plain_text": "Task 1"}]},"Status": {"select": {"name": "In Progress"}}}}],"has_more": false}
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.