Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Account Teams → Display Single Team Member Response Object

AI-generated

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, such as viewing their role, permissions, or profile details in the context of an account's team.

Practical examples include:

  • Fetching a team member’s details to verify their access level.
  • Displaying user information in a dashboard for account management.
  • Auditing team membership and roles programmatically.

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 (userId) whose response object is to be displayed.

Output

The output contains a JSON object representing the detailed response of the specified team member within the given account team. This typically includes all available data fields returned by the API about that member, such as user identifiers, roles, permissions, status, and other metadata related to the team membership.

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 Payhawk API.
  • The operation depends on the external Payhawk API endpoint that provides team member details.

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; transient errors may require retries.
  • Unexpected response structure: If the API changes, the node might not parse the response correctly; updating the node or API specification may be necessary.

Links and References

Discussion