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 details of a card, such as adjusting the remaining budget or correcting card metadata. For example, if a company issues virtual cards to employees and wants to update the available funds on a specific card after expenses, this node can perform that update programmatically.

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 returned from the API after the update operation. This typically includes the card's current state with updated fields such as the new budget left. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating requests to the external service managing cards.
  • The node uses a base URL configured in credentials to send HTTP requests.
  • Depends on the external API described in the bundled OpenAPI specification (payhawk.api.json).

Troubleshooting

  • Missing Required Fields: If "Account Id" or "Card Id" are not provided, the node will fail because these identifiers are necessary to locate the card to update.
  • Invalid Budget Value: Providing a non-numeric or negative value for "Budget Left" may cause the API to reject the request.
  • Authentication Errors: Ensure the API key credential is correctly set up and has permissions to update cards.
  • Network Issues: Connectivity problems or incorrect base URL configuration can lead to request failures.

Links and References

  • Refer to the external API documentation for detailed information about card management endpoints.
  • n8n documentation on how to configure API credentials and use HTTP request nodes for similar integrations.

Discussion