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 operation retrieves a list of cards associated with a specified account. It is useful in scenarios where you need to fetch card details for an account, such as displaying card information in dashboards, processing card-related transactions, or managing card statuses programmatically.
For example, you might use this node to:
- Get all active cards for a user’s account.
- Filter cards by status or user ID.
- Paginate through large sets of cards by skipping and taking a subset of results.
Properties
| Name | Meaning |
|---|---|
| Account Id | Identifier of the account whose cards you want to retrieve. |
| Filter | JSON-stringified and URL-encoded filter expression object that conforms to the card filter schema. Used to specify conditions like userId, status, and logical combinations to narrow down the results. |
| Skip | Number of card objects to skip from the beginning of the result set. Useful for pagination. |
| Take | Maximum number of card objects to return. Limits the size of the result set. |
Output
The output contains a JSON array of card objects matching the query parameters. Each card object includes details such as card identifiers, user associations, status, and other relevant card metadata depending on the API response schema.
No binary data output is indicated for this operation.
Dependencies
- Requires connection to the external API service that manages card data (referred to generically here).
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL for the API must be set in the node credentials or environment configuration.
Troubleshooting
- Empty Results: If no cards are returned, verify that the
Account Idis correct and that the filter criteria are not overly restrictive. - Invalid Filter Format: Ensure the filter JSON is properly stringified and URL-encoded; malformed filters may cause request failures.
- Authentication Errors: Check that the API key or token is valid and has sufficient permissions to access card data.
- Pagination Issues: When using
SkipandTake, ensure values are within valid ranges and consistent with the total number of available cards.
Links and References
- Refer to the external API documentation for detailed card filter schema (
ICardFilter) and supported query parameters. - Consult n8n documentation on how to configure API credentials and use JSON input properties effectively.