Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

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 a dashboard.

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
Card Id Identifier of the card to get

Both properties are required inputs to specify exactly which card's information should be retrieved.

Output

The node outputs JSON data representing the card's details. This typically includes all relevant fields returned by the API for the specified card, such as card number (masked), status, limits, expiration date, and any metadata associated with the card.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential for authentication with the external service.
  • The node uses a base URL configured via credentials to connect to the API endpoint.
  • The underlying implementation depends on an OpenAPI specification bundled within the node for request construction.

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 credential is correctly set up and has sufficient permissions.
  • Network issues: Check connectivity to the API base URL.
  • Unexpected API responses: Confirm that the API version matches the node’s expectations and that the card exists under the given account.

Links and References

  • Refer to the external API documentation for detailed card object schema and additional query parameters.
  • Consult n8n documentation on setting up API credentials and using HTTP-based nodes.

Discussion