Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node operation, "Display Team Members Response Object" under the "Account Teams" resource, is designed to retrieve and display information about members of a specific team within an account. It is useful in scenarios where you need to manage or audit team membership, such as verifying who belongs to a team, managing permissions, or integrating team data into workflows.

For example, a user might use this node to fetch all members of a sales team in an account to send targeted notifications or generate reports on team composition.

Properties

Name Meaning
Account Id Identifier of the account. This specifies which account's team members are being queried.
Team Id Identifier of the team. This specifies the particular team within the account to display members for.

Output

The output of this node will be a JSON object representing the response containing the team members' details. The structure typically includes member identifiers, names, roles, and possibly other metadata related to each team member.

If the node supports binary data output (not evident from the provided code), it would generally represent attachments or files related to team members, but no such indication is present here.

Dependencies

  • Requires an API key credential or similar authentication token configured in n8n to access the external service.
  • Depends on the external API described by the bundled OpenAPI specification (payhawk.api.json).
  • The node uses standard HTTP headers for JSON communication (Accept: application/json, Content-Type: application/json).
  • Base URL for API requests is dynamically set from credentials.

Troubleshooting

  • Missing or invalid Account Id or Team Id: Ensure both identifiers are correctly provided; otherwise, the API call will fail or return empty results.
  • Authentication errors: Verify that the API key or authentication token is valid and has sufficient permissions to access team data.
  • Network issues: Check connectivity to the API endpoint specified in credentials.
  • Unexpected response format: If the API changes, the node may not parse responses correctly; updating the OpenAPI spec or node version may be necessary.

Links and References

  • Refer to the external API documentation corresponding to the Payhawk service for detailed information on team member endpoints.
  • n8n documentation on creating and using custom nodes with OpenAPI specifications.

Discussion