Actions16
Overview
The node provides advanced integration with the Notion API, supporting multiple resources including pages, blocks, databases, and users. Specifically for the User resource with the List operation, it retrieves a list of all users available in the connected Notion workspace.
This node is beneficial when you need to programmatically access user information from Notion, such as for auditing, reporting, or assigning tasks based on user data. For example, you could use this node to fetch all users and then filter or notify them within an automated workflow.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | A collection of optional fields that can be added when creating or updating pages (not applicable for User List operation). Options include: Icon (emoji or image URL), Cover (page cover image URL), Archive (boolean to archive the page). |
Note: For the User - List operation, no additional input properties are required beyond selecting the resource and operation.
Output
- The output JSON contains a list of user objects retrieved from Notion.
- The structure includes:
results: An array of user objects, each representing a Notion user with their details.count: The total number of users returned.
Example output structure (simplified):
{
"results": [
{
"id": "user-id-1",
"name": "User One",
"avatar_url": "https://...",
"type": "person",
...
},
{
"id": "user-id-2",
"name": "User Two",
"avatar_url": "https://...",
"type": "person",
...
}
],
"count": 2
}
- The node does not output binary data for this operation.
Dependencies
- Requires valid Notion API credentials configured in n8n to authenticate requests.
- Uses Notion's official API endpoints to fetch user data.
- No additional external services are needed beyond the Notion API.
Troubleshooting
- Invalid Notion API credentials: The node will throw an error if the provided API credentials are invalid or expired. Ensure your API key or token is correct and has sufficient permissions.
- API rate limits: If many users exist or multiple requests are made rapidly, you might hit Notion API rate limits. Implement retry logic or reduce request frequency.
- Empty results: If the workspace has no users or the API returns empty, verify that the connected Notion workspace is correct and accessible.
- Network issues: Connectivity problems may cause request failures; check your network and proxy settings if applicable.