NotionSettings
| Setting | What it is |
|---|---|
| ConnectionRequired | The integration needs the Read user information capability for this — set it in Notion under the integration's Capabilities. |
| People per call | number |
| Fetch every page | Follows Notion's cursor, and refuses past 5,000 people rather than answering a short list. |
| Cursor | Paste a previous run's Next cursor to read the page after it. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `notion`) |
limit | number, by default 100 |
returnAll | true/false, by default false |
cursor | text |
Output
| Field | Type |
|---|---|
usersPeople | array |
userCountPeople in this answer | number |
hasMoreMore people are waiting behind this page | boolean |
nextCursorCursor for the next page | string |
Sample output, and the expression for each field
- hasMorefalse
- nextCursor""
- userCount0
- users[]
Errors
When a step of this node stops a run, the run page shows a code. Look it up:
Example step
The step as a flow file holds it. Replace each value in <…>.
{
"config": {
"connection": "<connection id>",
"cursor": "",
"limit": 100,
"returnAll": false
},
"label": "List users",
"type": "notion.listUsers",
"version": 2
}Older versions
A flow that already has this version keeps running it. A new step always gets the newest.
Version 1
| Setting | What it is |
|---|---|
| ConnectionRequired | The integration needs the Read user information capability for this — set it in Notion under the integration's Capabilities. |
| People per call | number |
| Fetch every page | Follows Notion's cursor, and refuses past 5,000 people rather than answering a short list. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `notion`) |
limit | number, by default 100 |
returnAll | true/false, by default false |