Actions99
- Expenses Actions
- Group Accounts Actions
- Group Account Codes Actions
- Accounts 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 programmatically manage card states, such as activating a new card, blocking a lost or stolen card, or closing a card that is no longer needed. For example, a finance team could automate blocking cards immediately when suspicious activity is detected 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 output does not include binary data.
Dependencies
- Requires an API key credential for authenticating requests to the external card management service.
- The node uses a base URL configured in the credentials to send HTTP requests.
- The node depends on the external card management API to perform the status update operation.
Troubleshooting
- Invalid Account Id or Card Id: If these identifiers are incorrect or do not exist, the API will likely return an error indicating the resource was not found. Verify the IDs before running the node.
- Unauthorized or Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions to update card statuses.
- Invalid Status Value: Only "active", "blocked", or "closed" are accepted. Providing any other value will cause the request to fail.
- Network Issues: Connectivity problems with the external API endpoint can cause timeouts or failures. Check network access and API availability.
Links and References
- Refer to the external card management API documentation for detailed information about card status values and their effects.
- Consult n8n documentation on how to configure API key credentials and handle HTTP request errors.