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
This node allows you to decline a pending request in the Qonto system. It is useful when you want to programmatically reject specific requests related to financial operations such as flash cards, virtual cards, transfers, or multi-transfers. For example, if a transfer request is no longer valid or authorized, you can use this node to decline it and optionally provide a note explaining the reason.
Common scenarios include:
- Automatically declining expired or suspicious card requests.
- Rejecting transfer requests that do not meet compliance rules.
- Managing bulk multi-transfer requests by declining invalid ones.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use for the API call. Options: "Login and Secret-Key" or "OAuth2". |
| ID | The unique identifier (UUID) of the request to be declined. This specifies which request will be processed. |
| Request_type | The type of request to decline. Options are: - Flash_cards: Non-physical cards with a budget and expiry date. - Virtual_cards: Non-physical cards with monthly budgets. - Transfers: Money transfers between accounts. - Multi_transfers: Multiple transfers executed simultaneously. |
| Declined Note | A required string note explaining why the request is being declined. This note is sent along with the decline action. |
Output
The output is a JSON object representing the response from the Qonto API after attempting to decline the specified request. It typically contains details about the declined request status or any error messages returned by the API.
No binary data output is produced 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.
- Uses UUID generation internally to create idempotency keys for safe API calls.
Troubleshooting
- Missing or invalid ID: If the provided request ID is incorrect or missing, the API will return an error indicating the request cannot be found. Ensure the UUID is correct.
- Invalid request type: Using a request type not supported by the API will cause failure. Confirm the request type matches one of the allowed options.
- Authentication errors: If credentials are invalid or expired, the API will reject the request. Verify your API key or OAuth2 token is correctly set up.
- Declined Note missing: Since the declined note is required, omitting it will likely cause validation errors. Always provide a meaningful note.
- Idempotency key conflicts: Although the node generates unique idempotency keys automatically, repeated identical requests might be rejected if the key is reused improperly.
Links and References
- Qonto API Documentation – Official API docs for detailed request and response formats.
- UUID npm package – Used internally for generating unique idempotency keys.