Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Cards → Get Card

AI-generated

Overview

This node retrieves detailed information about a specific card associated with an account. It is useful in scenarios where you need to fetch the current state or metadata of a particular card, such as verifying card details before processing transactions, auditing card usage, or displaying card information in dashboards.

For example, you might use this node to get the details of a corporate credit card by providing the account and card identifiers, enabling you to check its status, limits, or other attributes.

Properties

Name Meaning
Account Id Identifier of the account to which the card belongs. This is required to specify the context for the card retrieval.
Card Id Identifier of the specific card to retrieve. This uniquely identifies the card within the given account.

Output

The node outputs a JSON object containing the details of the requested card. The structure typically includes all relevant card information such as card number (masked), status, limits, expiration date, and any metadata provided by the API.

If the node supports binary data output (not indicated here), it would typically represent card-related documents or images, but based on the code and properties, the output is purely JSON.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the external service.
  • The node depends on an external REST API described by an OpenAPI specification (payhawk.api.json).
  • Proper configuration of the base URL and authentication credentials is necessary for successful operation.

Troubleshooting

  • Missing or invalid Account Id/Card Id: Ensure both identifiers are provided and correct; otherwise, the API will return errors indicating resource not found.
  • Authentication errors: Verify that the API key or authentication token is correctly set up in n8n credentials.
  • Network issues or incorrect base URL: Confirm that the base URL is properly configured and reachable.
  • API rate limits or permissions: Check if the API user has sufficient permissions to access card details and that rate limits have not been exceeded.

Links and References

  • Refer to the external API documentation for detailed card object schema and additional parameters.
  • n8n documentation on setting up API credentials and using HTTP request nodes may be helpful for troubleshooting connection issues.

Discussion