Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation retrieves detailed information about a single team member within a specific team of an account. It is useful when you need to display or process the data of one particular member in an account's team, such as viewing their role, status, or other profile details.

Practical examples include:

  • Fetching a team member’s profile to verify their permissions.
  • Displaying user details in a dashboard or report.
  • Auditing team membership for compliance or management purposes.

Properties

Name Meaning
Account Id Identifier of the account from which the team member belongs.
Team Id Identifier of the team within the account where the member is part of.
Member Id Identifier of the specific team member (corresponds to userId in the external system).

Output

The output is a JSON object representing the detailed response of the requested team member. This typically includes all available fields describing the member, such as their ID, name, email, role, status, and any other metadata provided by the external API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the external service.
  • The node uses a base URL configured via credentials to connect to the external API.
  • The operation depends on the external API endpoint that returns team member details based on account, team, and member identifiers.

Troubleshooting

  • Missing or invalid identifiers: Ensure that Account 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 authentication token is valid and has sufficient permissions to access team member data.
  • Network or API errors: Check connectivity and API availability; handle rate limits or downtime gracefully.
  • Unexpected response structure: If the output JSON does not match expectations, confirm that the API version and endpoint have not changed.

Links and References

  • Refer to the external API documentation for "Account Teams" and "Team Member" endpoints for detailed schema and usage.
  • Consult n8n documentation on configuring API credentials and using HTTP request nodes for custom integrations.

Discussion