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 manage insurance contracts and other financial resources. Specifically, for the "Insurance Contract" resource and the operation "Upload a PDF Document for a Specific Insurance Contract," it allows users to upload a PDF file associated with a particular insurance contract by specifying its unique contract ID.
Common scenarios where this node is beneficial include:
- Automating document management by attaching policy documents or contract PDFs directly to insurance contracts.
- Centralizing contract documentation within workflows that handle insurance data.
- Streamlining compliance processes by ensuring all contract-related files are uploaded and stored in one place.
For example, an insurance company could use this node to automatically upload signed contract PDFs received via email into their Qonto insurance contract records.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to access the API: either "Login and Secret-Key" or "OAuth2". |
| Contract ID | The unique identifier of the insurance contract to which the PDF will be uploaded. |
| PDF File | Path to the PDF file that will be uploaded and attached to the specified insurance contract. |
Output
The node outputs JSON data representing the response from the Qonto API after uploading the PDF document. This typically includes confirmation details about the uploaded file and its association with the insurance contract.
No binary data output is produced by this operation; the output is purely JSON-formatted metadata about the upload result.
Dependencies
- Requires access to the Qonto API.
- Requires valid authentication credentials configured in n8n, either via an API key credential or OAuth2 token.
- The node expects the PDF file path to be accessible and readable by the workflow environment.
Troubleshooting
Common issues:
- Invalid or missing Contract ID: Ensure the contract ID provided exists and is correct.
- Incorrect file path or inaccessible PDF file: Verify the file path is correct and the file is accessible.
- Authentication errors: Confirm that the API credentials are correctly set up and have sufficient permissions.
- API rate limits or network issues may cause request failures.
Error messages:
- Errors related to missing parameters usually indicate required fields like Contract ID or PDF File are empty.
- Authentication failures will mention unauthorized access or invalid tokens/keys.
- File upload errors might indicate problems reading the file or incorrect content type.
Resolving these generally involves verifying input parameters, checking credentials, and ensuring the file is properly accessible.
Links and References
- Qonto API Documentation (for detailed API endpoints and authentication)
- n8n Documentation on Creating Custom Nodes