Actions99
- Group Accounts Actions
- Group Account Codes Actions
- Accounts Actions
- Expenses Actions
- Purchase Orders Actions
- Get A List Of Purchase Orders
- Create A New Purchase Order
- Get A Purchase Order
- Update A Purchase Order
- Open A Purchase Order
- Get A List Of Purchase Orders Items For A Specific Purchase Order
- Create A Purchase Order Item
- Get A Purchase Order Item
- Update A Purchase Order Item
- Delete A Purchase Order Item
- Get A List Of Goods Received Notes For A Specific Purchase Order
- Create A Goods Received Note
- Attach A File To A Goods Received Note
- Delete A Goods Received Note
- Suppliers Actions
- Fund Accounts Actions
- Cards Actions
- Expense Categories Actions
- Tax Rates Actions
- Amortizations Actions
- Account Teams Actions
- Account Codes Actions
- External Teams Actions
- Custom Fields Actions
- Get Custom Fields
- Create A New Custom Field
- Get Custom Field
- Update Custom Field
- Delete A Custom Field And All Its Values
- Get Custom Field Values
- Create A Custom Field Value
- Delete Custom Field Values
- Get A Custom Field Value
- Update A Custom Field Value
- Delete A Custom Field Value
- Get Managers For A Specific Custom Field Value
- Adds Managers For A Specific Custom Field Value
- Replaces Managers For A Specific Custom Field Value
- Removes Managers For A Specific Custom Field Value
- Webhook Subscriptions Actions
- Group Teams Actions
Cards → Update Card
AI-generatedOverview
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 reflecting changes in available funds.
Practical examples include:
- Updating the remaining budget on a corporate expense card after a transaction.
- Modifying card details when reallocating funds between departments.
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. This typically includes the card's current state after the update, such as its ID, associated account, and updated budget information.
If the node supports binary data output, it would represent any file or media related to the card, but based on the provided code and properties, this node primarily deals with JSON data.
Dependencies
- Requires an API key credential for authenticating requests to the external service managing cards.
- Needs configuration of the base URL for the API endpoint.
- Depends on the external API described by the bundled OpenAPI specification (
payhawk.api.json).
Troubleshooting
- Missing Required Fields: Ensure "Account Id" and "Card Id" are provided; otherwise, the API will reject the request.
- Invalid Budget Value: The "Budget Left" must be a valid number; non-numeric inputs may cause errors.
- Authentication Errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network Issues: Check connectivity to the API base URL and ensure no firewall or proxy blocks the request.
Common error messages might include:
- Unauthorized access due to invalid credentials.
- Not found errors if the specified account or card IDs do not exist.
- Validation errors if input values do not meet API requirements.
Resolving these usually involves verifying input parameters, credentials, and network settings.
Links and References
- Refer to the external API documentation for detailed information on card management endpoints.
- n8n documentation on creating and configuring HTTP request nodes for API interaction.