Qonto

Consume Qonto API

Actions46

Attachment Actions
- Upload Attachment
- Show Attachment
Attachments in a Transaction Actions
Beneficiary Actions
Card Actions
Client Actions
Client Invoice Actions
Credit Note Actions
- Get a List of Credit Notes for an Organization
- Get Details of Credit Note for an Organization
External Transfer Actions
Insurance Contract Actions
Internal Transaction Actions
- Create Internal Transfer
Label Actions
- List Labels
- Show Label
Membership Actions
Organization Actions
- Get Organization and Its Bank_accounts
Request Actions
Statement Actions
- Show Statement
- List Statements
Supplier Invoice Actions
- Get a List of Supplier Invoices for an Organization
- Create Supplier Invoices with Attachments
Team Actions
- List Teams in an Organization
- Create a New Team
Transaction Actions
- List Transactions
- Show Transaction

Overview

This node integrates with the Qonto API to manage insurance contracts among many other resources. Specifically, the "Get Insurance Contract" operation fetches detailed information about a single insurance contract by its unique identifier. This is useful in scenarios where you need to retrieve contract details for review, reporting, or further processing within an automation workflow.

Practical examples include:

Automatically retrieving insurance contract details when a new client is onboarded.
Fetching contract data to validate coverage before processing claims.
Integrating contract information into financial or CRM systems.

Properties

Name	Meaning
Authentication	Method of authenticating with the Qonto API. Options: "Login and Secret-Key", "OAuth2".
Contract ID	The unique identifier of the insurance contract to be fetched. Required for this operation.

Output

The output is a JSON array containing the insurance contract data returned from the Qonto API. The structure corresponds directly to the API response for a single insurance contract, typically including fields such as contract name, start and end dates, coverage details, and other metadata related to the contract.

No binary data output is produced by this operation.

Dependencies

Requires access to the Qonto API.
Requires configuration of authentication credentials in n8n, either via an API key credential or OAuth2 token.
Uses internal helper functions to make authenticated HTTP requests to the Qonto API endpoints.

Troubleshooting

Missing or invalid Contract ID: The operation requires a valid contract ID; ensure it is provided and correct.
Authentication errors: Verify that the selected authentication method is properly configured and the credentials are valid.
API request failures: Network issues or API rate limits may cause errors; check connectivity and API usage quotas.
Unexpected API responses: If the API changes or returns unexpected data, the node might fail; verify API version compatibility.

Links and References

Qonto API Documentation (for detailed API endpoint info)
n8n documentation on Creating Custom Nodes