Notion Advanced

Full-featured Notion node with exhaustive block and formatting support using existing credentials

Overview

The node "Notion Advanced" provides comprehensive integration with the Notion API, enabling advanced operations on Notion resources such as pages, blocks, databases, and users. Specifically, for the User resource with the List operation, this node fetches a list of all users available in the connected Notion workspace.

This functionality is useful when you want to retrieve user information for purposes like assigning tasks, managing permissions, or auditing user activity within Notion. For example, you might use this node to get a roster of all users to display in a dashboard or to automate notifications based on user data.

Properties

Name Meaning
Additional Fields Collection of optional fields applicable mainly to page operations (not used in User List)

For the User - List operation, no additional input properties are required beyond selecting the resource and operation.

Output

The output JSON structure for the User - List operation contains:

  • results: An array of user objects retrieved from Notion.
  • count: The total number of users returned.

Each user object typically includes details such as user ID, name, avatar URL, type (person or bot), and other metadata as provided by the Notion API.

No binary data output is involved in this operation.

Example output snippet:

{
  "results": [
    {
      "id": "user-id-1",
      "name": "John Doe",
      "avatar_url": "https://example.com/avatar.jpg",
      "type": "person"
    },
    {
      "id": "user-id-2",
      "name": "Jane Smith",
      "avatar_url": null,
      "type": "bot"
    }
  ],
  "count": 2
}

Dependencies

  • Requires valid Notion API credentials configured in n8n to authenticate requests.
  • Uses the Notion API endpoint /users with pagination support internally.
  • No additional external dependencies beyond the Notion API and n8n environment.

Troubleshooting

  • Invalid Notion API credentials: The node validates credentials before execution. If invalid, it throws an error. Ensure your API key or token is correctly set up in n8n credentials.
  • API rate limits: If many users exist, repeated calls may hit Notion's rate limits. Consider adding delays or handling errors gracefully.
  • Empty results: If no users are returned, verify that your Notion workspace has users and that your API token has sufficient permissions.
  • Network issues: Connectivity problems can cause request failures. Check network access and proxy settings if applicable.

Links and References


This summary focuses exclusively on the User resource with the List operation as requested.

Discussion