Actions67
- Archive Document Actions
- Cashbook Actions
- Client Actions
- Company Actions
- E-Invoice Actions
- Email Actions
- Info Actions
- Issued Document Actions
- Product Actions
- Receipt Actions
- Received Document Actions
- Setting Actions
- Supplier Actions
- Tax (F24) Actions
- Webhook Actions
Overview
This node integrates with the Fatture in Cloud API, specifically allowing users to manage webhook subscriptions among many other resources. The Webhook - Get operation retrieves details about a specific webhook subscription for a given company.
Typical use cases include:
- Fetching information about an existing webhook subscription to verify its configuration.
- Monitoring webhook subscriptions programmatically as part of automation workflows.
- Integrating webhook management into broader business process automations involving invoicing, clients, or company data.
For example, a user might want to retrieve the details of a webhook subscription by providing the company ID and the subscription ID to confirm that the webhook is active and correctly set up.
Properties
| Name | Meaning |
|---|---|
| Company ID | The numeric identifier of the company for which the webhook subscription belongs. |
| Subscription ID | The unique string identifier of the webhook subscription to retrieve. |
Output
The node outputs JSON data representing the webhook subscription details retrieved from the Fatture in Cloud API. This typically includes fields such as subscription metadata, event types subscribed to, callback URLs, status, and other relevant webhook configuration details.
If the node encounters an error during execution, it outputs an error object containing message, status code, status text, and any additional data returned by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an API authentication credential (OAuth2 token) configured in n8n to access the Fatture in Cloud API.
- Network connectivity to the Fatture in Cloud service endpoint.
- The node depends on internal modules corresponding to each resource; for webhooks, it uses a dedicated WebhooksModule to perform the API calls.
Troubleshooting
Common issues:
- Invalid or expired API credentials will cause authentication failures.
- Providing incorrect company ID or subscription ID will result in "not found" or similar errors.
- Network issues or API downtime can cause request failures.
Error messages:
Fatture in Cloud API Error: <message>indicates an error response from the API. The message usually contains the reason, e.g., invalid parameters or unauthorized access.- If the node is set to continue on fail, errors are returned as JSON objects in the output stream instead of stopping execution.
Resolution tips:
- Verify that the API credentials are valid and have sufficient permissions.
- Double-check the company ID and subscription ID values.
- Ensure stable internet connection and that the Fatture in Cloud API service is operational.
Links and References
- Fatture in Cloud API Documentation (official API docs)
- n8n Documentation for general usage and credential setup