Actions45
- Attachment Actions
- Beneficiary Actions
- Business Account Actions
- Card Actions
- Client Actions
- Client Invoice Actions
- Credit Note Actions
- External Transfer Actions
- Insurance Contract Actions
- Internal Transfer Actions
- Label Actions
- Membership Actions
- Organization Actions
- Quote Actions
- Request Actions
- SEPA Transfer Actions
- Statement Actions
- Supplier Invoice Actions
- Team Actions
- Transaction Actions
Overview
This node integrates with the Qonto API, allowing users to interact with various Qonto resources. Specifically, for the Card resource with the Get One operation, it retrieves detailed information about a single card by its unique ID. This is useful in scenarios where you need to fetch specific card details such as card status, limits, or transaction history for reporting, auditing, or automation workflows.
Practical examples include:
- Fetching card details to verify card status before processing payments.
- Retrieving card information to display in dashboards or internal tools.
- Automating compliance checks by pulling card metadata.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with the Qonto API. Options: API Key |
| ID | The unique identifier of the card resource to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the card resource retrieved from the Qonto API. The structure typically includes fields such as card ID, status, type, limits, owner information, and other metadata related to the card.
If the node supports binary data output (not explicitly shown here), it would represent any associated files or attachments related to the card, but this is not indicated in the provided code.
Dependencies
- Requires an active Qonto API key credential for authentication.
- The node uses the Qonto API endpoints, switching between sandbox and production environments based on configuration.
- No additional external dependencies are indicated beyond the Qonto API access.
Troubleshooting
Common issues:
- Invalid or missing card ID will cause errors when retrieving the card.
- Incorrect or expired API key will result in authentication failures.
- Network timeouts or connectivity issues may prevent successful API calls.
Error messages:
"Unknown resource: card"— indicates the resource name was not recognized; ensure "card" is correctly specified.- API error messages returned from Qonto will be passed through; check the message for details like invalid ID or permission issues.
Resolutions:
- Verify the card ID is correct and exists in your Qonto account.
- Confirm that the API key credential is valid and has necessary permissions.
- Check network connectivity and retry if transient errors occur.