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
Overview
This node updates the status of a specific card within an account. It is useful in scenarios where you need to manage card lifecycle states such as activating a new card, blocking a compromised card, or closing a card that is no longer in use. For example, a finance team could automate blocking cards reported lost or stolen, or close cards when employees leave the company.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account to which the card belongs. |
| Card Id | Identifier of the card whose status you want to update. |
| Status | Requested card status. Options: Active (enable card usage), Blocked (temporarily disable), Closed (permanently deactivate). |
Output
The node outputs JSON data representing the updated card information after the status change. This typically includes confirmation of the new status and may contain other card details returned by the API. The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating requests to the external card management service.
- The base URL for the API must be configured in the node credentials or environment.
- The node uses HTTP requests with JSON payloads to communicate with the external service.
Troubleshooting
- Invalid Account Id or Card Id: Ensure the identifiers are correct and exist in the system; otherwise, the API will return errors indicating resource not found.
- Unauthorized Errors: Verify that the API key or authentication token is valid and has sufficient permissions to update card statuses.
- Invalid Status Value: Only "active", "blocked", or "closed" are accepted. Providing other values will cause request failures.
- Network Issues: Check connectivity to the API endpoint and ensure no firewall or proxy blocks the requests.
Links and References
- Refer to your card management service API documentation for detailed explanations of card statuses and error codes.
- n8n documentation on creating and using API credentials for secure authentication.