Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node interacts with a service managing groups and teams, specifically allowing you to retrieve detailed information about a single team member within a specified team and group. It is useful in scenarios where you need to fetch user details for auditing, reporting, or integration purposes, such as displaying member profiles in dashboards or syncing user data with other systems.

For example, if you manage multiple teams within an organization and want to get the profile of a particular member in a specific team, this node will let you specify the group, team, and member identifiers to fetch that exact user's data.

Properties

Name Meaning
Group Id Identifier of the Group. The unique ID representing the group containing the team.
Team Id Identifier of the Team. The unique ID representing the team within the group.
Member Id Identifier of the Member (userId in Payhawk). The unique ID of the team member to fetch.

Output

The node outputs a JSON object representing the detailed response of the requested team member. This typically includes all available information about the member as returned by the external API, such as user profile details, roles, status, and any metadata associated with the member in the team context.

No binary data output is indicated by the source code.

Dependencies

  • Requires connection to an external API service managing groups, teams, and members.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The base URL for the API is expected to be set in the credentials configuration.
  • Uses standard HTTP headers for JSON communication (Accept: application/json, Content-Type: application/json).

Troubleshooting

  • Missing or incorrect IDs: Ensure that the Group Id, Team Id, and Member Id are correctly provided and correspond to existing entities in the external system.
  • Authentication errors: Verify that the API key or token is valid and has sufficient permissions to access group/team/member data.
  • Network issues: Check connectivity to the API endpoint and confirm the base URL is correctly configured.
  • Unexpected API responses: If the API changes or returns errors, review the error message for clues and update the node configuration accordingly.

Links and References

  • Refer to the external API documentation for groups, teams, and members to understand the structure of the response and required identifiers.
  • n8n documentation on setting up API credentials and HTTP request nodes may help configure authentication properly.

Discussion