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 interacts with the Qonto API to retrieve detailed information about a specific label within an organization. The "Show Label" operation fetches data for a single label identified by its unique ID. This is useful in scenarios where you need to access or verify label details, such as categorizing transactions or managing organizational tags.
Practical examples include:
- Fetching label details to display in a dashboard.
- Using label information to filter or organize financial data.
- Integrating label metadata into automated workflows for accounting or reporting.
Properties
Name | Meaning |
---|---|
Authentication | Method of authenticating with the Qonto API. Options: "Login and Secret-Key", "OAuth2". |
ID | The unique identifier of the label to retrieve. |
Output
The node outputs a JSON object representing the label's details as returned by the Qonto API. This typically includes properties such as the label's ID, name, color, and any other metadata associated with the label in the organization.
No binary data output is involved in this operation.
Dependencies
- Requires access to the Qonto API.
- Requires authentication credentials configured 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
- Invalid or missing ID: If the provided label ID is incorrect or not found, the API will return an error. Ensure the ID is valid and exists in the organization.
- Authentication errors: Incorrect or expired credentials will cause authentication failures. Verify that the API key or OAuth2 token is correctly set up and has necessary permissions.
- API rate limits: Excessive requests may trigger rate limiting. Implement retry logic or reduce request frequency if needed.
- Network issues: Connectivity problems can cause request failures. Check network status and proxy settings if applicable.