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 is designed to retrieve detailed information about a specific card associated with an account. It is useful in scenarios where you need to fetch the current state or details of a particular card, such as its status, limits, or metadata. For example, a finance team might use this node to verify card details before approving transactions or to audit card usage.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account |
| Card Id | Identifier of the card to get |
Both properties are required inputs and must be provided to successfully retrieve the card information.
Output
The output will contain a JSON object representing the card's details. This typically includes fields such as card identifiers, status, limits, and other metadata related to the card. The exact structure depends on the API response but generally provides comprehensive information about the requested card.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential for authentication to the external service managing cards.
- The node expects the base URL of the API to be configured in the credentials.
- The node uses standard HTTP headers for JSON communication (
Accept: application/json,Content-Type: application/json).
Troubleshooting
- Missing or invalid Account Id/Card Id: Ensure both identifiers are correctly provided; otherwise, the API will likely return an error indicating missing or invalid parameters.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions to access card data.
- Network issues or incorrect base URL: Confirm that the base URL in the credentials is correct and reachable.
- API rate limits or service downtime: If requests fail repeatedly, check for rate limiting or service availability issues.
Links and References
- Refer to the external API documentation for detailed card object schema and additional query options.
- Consult n8n documentation on setting up API key credentials and configuring HTTP request nodes for further customization.