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 integrates with the Qonto API to create new virtual cards of different types (Virtual, Flash, Advertising) for a specified organization. It is useful in scenarios where businesses want to programmatically issue virtual payment cards for employees, advertising campaigns, or other specific purposes without needing physical cards. For example, a company can automate issuing virtual cards with spending limits and currency settings for team members or marketing budgets.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication: "Login and Secret-Key" or "OAuth2" |
| Organization ID | The unique identifier of the organization for which the virtual card will be created |
| Card Type | The type of virtual card to create; options are: Virtual, Flash, Advertising |
| Card Name | The name assigned to the virtual card |
| Spending Limit | Optional numeric value specifying the spending limit for the virtual card |
| Currency | The currency code (e.g., EUR) for the virtual card |
Output
The output is a JSON array containing the response from the Qonto API after creating the virtual card. This typically includes details about the newly created card such as its ID, type, name, spending limit, currency, status, and other metadata returned by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Qonto API.
- Requires either OAuth2 or Login and Secret-Key authentication configured in n8n credentials.
- Uses UUID generation for idempotency keys internally (not exposed as input).
- No additional external dependencies beyond the Qonto API and n8n environment.
Troubleshooting
- Missing or invalid Organization ID: Ensure the organization ID is correct and that the authenticated user has permission to create cards for it.
- Invalid Card Type: Use one of the supported card types: Virtual, Flash, or Advertising.
- Spending Limit issues: If provided, ensure the spending limit is a valid number and within allowed limits set by Qonto.
- Authentication errors: Verify that the selected authentication method is properly configured and the credentials are valid.
- API rate limits or network errors: These may cause request failures; check connectivity and Qonto API status.
- Common error messages from the API will be passed through; reading the message usually indicates the problem (e.g., unauthorized, bad request).
Links and References
- Qonto API Documentation
- n8n Documentation on Credentials
- UUID npm package (used internally for idempotency keys)