Actions26
- Board Actions
- Docs Actions
- Folder Actions
- Group Actions
- Item Actions
- Updates Actions
- Users Actions
Overview
This node operation lists users from a Monday.com account with flexible filtering and field selection options. It is useful for workflows that need to retrieve user information such as emails, IDs, roles, or team memberships. For example, you can use it to get all active members in a workspace, filter users by specific email addresses, or fetch detailed user profiles including photos and admin status.
Properties
| Name | Meaning |
|---|---|
| Filters | Collection of filters to narrow down the list of users: |
| - Emails | Filter by specific email addresses (comma-separated). |
| - User IDs | Filter by specific user IDs (comma-separated). |
| - User Type | Filter by user type. Options: All Users, Members (Non-Guests), Guests Only, Active Members. |
| - Limit | Maximum number of users to return (1 to 100). |
| - Name | Fuzzy search by user name. |
| - Newest First | Boolean flag to list most recently created users first. |
| Return Fields | Collection of fields to include in the output for each user: |
| - Include Email | Whether to include the user's email address. |
| - Include Account | Whether to include account information. |
| - Include Admin Status | Whether to include if the user has admin privileges. |
| - Include Guest Status | Whether to include if the user is a guest. |
| - Include Photo | Whether to include the profile photo URL. |
| - Include Teams | Whether to include the teams the user belongs to. |
| - Include Created At | Whether to include the user's creation date. |
Output
The output is an array of JSON objects, each representing a user matching the specified filters. Each user object contains fields based on the selected "Return Fields" properties, such as:
- Basic user info (e.g., id, name)
- Email address (if included)
- Account details (if included)
- Admin and guest status flags (if included)
- Profile photo URL (if included)
- Team memberships (if included)
- Creation timestamp (if included)
No binary data is output by this node.
Dependencies
- Requires an API token credential for Monday.com with appropriate permissions to read user data.
- The node uses the Monday.com API client internally to query user information.
- No additional environment variables are required beyond the API authentication setup.
Troubleshooting
- Empty results: Check that your filters are correctly formatted (e.g., comma-separated emails or IDs) and that the user type filter matches existing users.
- User not found error: When using the "Get" operation (not listed here but related), specifying a non-existent user ID will throw an error.
- API rate limits: If many users are requested repeatedly, you may hit API rate limits; consider limiting the number of users per request.
- Invalid JSON in filters: Ensure that any JSON input (if used elsewhere) is well-formed to avoid parsing errors.
- Permission issues: Make sure the API token has sufficient rights to access user data.