Actions46
- Attachment Actions
- Attachments in a Transaction Actions
- Beneficiary Actions
- Card Actions
- Client Actions
- Client Invoice Actions
- Credit Note Actions
- External Transfer Actions
- Insurance Contract Actions
- Internal Transaction Actions
- Label Actions
- Membership Actions
- Organization Actions
- Request Actions
- Statement Actions
- Supplier Invoice Actions
- Team Actions
- Transaction Actions
Overview
The "List Requests" operation of the Qonto node retrieves a list of requests from the Qonto API. This operation is useful for users who want to fetch and review various types of financial or administrative requests associated with their Qonto account, such as card requests, transfers, or other transaction-related requests.
Typical use cases include:
- Monitoring pending or approved requests to track their status.
- Filtering requests by type or date to generate reports or trigger workflows.
- Automating follow-up actions based on request statuses.
For example, a finance team could use this node to automatically pull all approved virtual card requests created after a certain date to reconcile expenses.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: "Login and Secret-Key" or "OAuth2". |
| Limit | Maximum number of results to return (minimum 1). Defaults to 50. |
| Filters | Collection of filters to narrow down the list of requests: - Status: Filter by request status. Allowed values are pending, approved, canceled, declined. Only one status can be selected at a time.- Request_type: Type of request to filter by. Options: • Flash_card: Non-physical card with a budget and expiry date. • Virtual_card: Non-physical card with a monthly budget. • Transfer: Money transfer between Qonto accounts. • Multi_transfer: Multiple transfers executed simultaneously. - Processed_at_from: Filter requests processed from this date/time. - Created_at_from: Filter requests created from this date/time. |
Output
The output is a JSON array containing the list of requests matching the specified filters. Each request object includes details such as its status, type, creation and processing dates, and other relevant metadata depending on the request type.
No binary data is output by this operation.
Dependencies
- Requires an active connection to the Qonto API.
- Requires either an API key credential ("Login and Secret-Key") or OAuth2 authentication configured in n8n.
- The node uses internal helper functions to handle API requests and pagination.
Troubleshooting
- Empty results: If no requests are returned, verify that the filters are correct and that there are requests matching those criteria in your Qonto account.
- Authentication errors: Ensure that the chosen authentication method is correctly configured and that the credentials have sufficient permissions.
- Invalid filter values: Using unsupported status or request_type values may cause errors or empty responses. Use only the allowed options.
- API rate limits: Frequent calls might hit Qonto API rate limits; consider adding delays or reducing the limit parameter.
Links and References
- Qonto API Documentation (for detailed API endpoints and request types)
- n8n Documentation (for general usage of nodes and credentials)