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 Status
AI-generatedOverview
This node operation updates the status of a specific card associated with 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 use this node to quickly block a lost card or close cards for employees who have left the company.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account to which the card belongs. |
| Card Id | Identifier of the card whose status needs to be updated. |
| Status | Requested card status. Options: Active, Blocked, Closed. Determines the new state of the card. |
Output
The node outputs JSON data representing the result of the update operation. This typically includes confirmation of the card's updated status and may contain other metadata about the card after the update. The output does not include binary data.
Dependencies
- Requires an API key credential for authenticating requests to the external card management service.
- The node expects a base URL configuration for the API endpoint.
- The node uses standard HTTP headers for JSON content type and accepts JSON responses.
Troubleshooting
- Common issues:
- Invalid or missing Account Id or Card Id will cause the update to fail.
- Providing an unsupported status value will result in an error.
- Network or authentication errors if the API key or base URL is misconfigured.
- Error messages:
- "Card not found" indicates the specified Card Id does not exist under the given Account Id.
- "Unauthorized" suggests invalid or missing API credentials.
- "Invalid status value" means the status provided is not one of the allowed options (Active, Blocked, Closed).
- Resolutions:
- Verify that Account Id and Card Id are correct and exist.
- Ensure the API key credential is valid and has necessary permissions.
- Confirm the status value matches one of the allowed options exactly.
Links and References
- Refer to your card management service API documentation for detailed information on card statuses and their effects.
- Consult n8n documentation on how to configure API credentials and environment variables for secure authentication.