Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation retrieves detailed information about a single team member within a specific account team. It is useful when you need to display or process the response object of an individual team member, for example, to verify their role, status, or other attributes in the context of an account's team management.

Practical scenarios include:

  • Fetching user details for auditing or reporting purposes.
  • Displaying team member information in a custom dashboard.
  • Integrating with other systems that require up-to-date team member data.

Properties

Name Meaning
Account Id Identifier of the account from which the team member belongs.
Team Id Identifier of the team within the account.
Member Id Identifier of the team member (corresponds to the user ID in the external system).

Output

The output contains a JSON object representing the detailed response of the specified team member. This typically includes all available fields returned by the external API about the member, such as their identifiers, roles, permissions, and possibly metadata related to their membership in the team.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the external service.
  • The base URL for the API must be configured in the node credentials.
  • Depends on the external API defined in the bundled OpenAPI specification (payhawk.api.json).

Troubleshooting

  • Missing or invalid identifiers: Ensure that the 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 credential is valid and has sufficient permissions to access team member data.
  • Network or API errors: Check connectivity and API availability; handle rate limits or service downtime gracefully.
  • Unexpected response structure: If the output JSON does not match expectations, confirm that the API version and node configuration align with the external service's current API.

Links and References

  • Refer to the external API documentation for detailed schema and field descriptions of the team member response object.
  • Consult n8n documentation on how to configure API credentials and use custom nodes with OpenAPI specifications.

Discussion