Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation retrieves the list of users associated with a specific account. It is useful in scenarios where you need to manage or audit user access within an account, such as fetching all users for review, synchronizing user data with another system, or automating user-related workflows.

For example, you might use this node to:

  • Get all users linked to a particular account to send notifications.
  • Audit user permissions by listing all account users.
  • Integrate with other systems that require up-to-date user lists from your accounts.

Properties

Name Meaning
Account Id Identifier of the account whose users you want to retrieve.
Filter JSON-stringified and URL-encoded filter expression object to narrow down the users returned. The filter must conform to the expected schema for account user filtering.

Output

The output contains a JSON array of user objects associated with the specified account. Each user object typically includes details such as user identifiers, names, roles, and other relevant metadata depending on the API's response structure.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to authorize requests against the external service.
  • The node uses a base URL provided via credentials to connect to the API endpoint.
  • The operation depends on the external API supporting account user retrieval with optional filtering.

Troubleshooting

  • Missing or invalid Account Id: Ensure the "Account Id" property is correctly set; otherwise, the API call will fail or return no results.
  • Incorrect filter format: The filter must be a valid JSON string and properly URL-encoded. Invalid filters may cause errors or unexpected results.
  • Authentication errors: Verify that the API key or authentication token is correctly configured and has sufficient permissions to access account user data.
  • API connectivity issues: Check network connectivity and the correctness of the base URL in credentials.
  • Empty results: If no users are returned, confirm that the account ID exists and that the filter (if used) matches existing users.

Links and References

  • Refer to the external API documentation for detailed information about the account user resource and supported filter schema.
  • Consult n8n documentation on how to configure API credentials and use JSON input properties effectively.

Discussion