List Users: Notion action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Page Size page_size	string	Optional	Number of users to return (max 100)

Sample request

{
  "page_size": "100"
}

Returns

{
  "object": "list",
  "results": [
    {
      "id": "user-id-123",
      "name": "Jane Doe",
      "type": "person",
      "object": "user",
      "person": {
        "email": "jane@example.com"
      },
      "avatar_url": "https://example.com/avatar.png"
    },
    {
      "id": "bot-id-456",
      "name": "My Integration",
      "type": "bot",
      "object": "user"
    }
  ],
  "has_more": false
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Users.

What does the List Users action do in Notion?

Lists all users in the connected Notion workspace with id, name, type, and avatar. Used to resolve a person field or to render a member picker.

What inputs does List Users require?

List Users has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Notion returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Users support batch operations?

Yes. Run List Users inside a Loop node to process arrays. Tiny Command handles Notion's rate limits automatically so you don't have to throttle manually.

More actions