Payhawk icon

Payhawk

Interact with the Zitadel API

Actions99

Overview

This node updates an existing card's information within an account. It is useful in scenarios where you need to modify the budget or other details of a card that has already been created, such as adjusting spending limits or correcting card data. For example, a finance team might use this node to update the remaining budget on a corporate card after expenses have been processed.

Properties

Name Meaning
Account Id Identifier of the account containing the card to update.
Card Id Identifier of the specific card to update.
Budget Left The amount of funds left on the card (numeric value).

Output

The node outputs JSON data representing the updated card object after the operation completes. This typically includes the card's current state with updated fields such as the new budget left and any other relevant card details returned by the API.

Dependencies

  • Requires an API key credential for authentication with the external service managing cards.
  • Needs the base URL of the API configured in the node credentials.
  • Depends on the external card management API to perform the update operation.

Troubleshooting

  • Missing or invalid Account Id/Card Id: Ensure these identifiers are correct and correspond to existing entities; otherwise, the API will return errors indicating not found or invalid parameters.
  • Invalid Budget Left value: Provide a valid numeric value; non-numeric or negative values may cause validation errors.
  • Authentication errors: Verify that the API key or authentication token is correctly set up and has sufficient permissions.
  • Network or API errors: Check connectivity and API status if requests fail unexpectedly.

Links and References

  • Refer to the external card management API documentation for detailed information on the update card endpoint and required parameters.
  • n8n documentation on creating and using custom nodes for API integrations.

Discussion