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
The node integrates with the Fatture in Cloud API to manage webhooks related to a company’s events. Specifically, the Webhook - Create operation allows users to create a new webhook subscription for a specified company. This webhook listens for certain event types (like creation, modification, or deletion of resources) and sends notifications to a defined URL endpoint ("sink").
This node is beneficial when you want to automate workflows triggered by changes in your Fatture in Cloud account data. For example, you can automatically update your CRM when a client is created or modified, or trigger alerts when invoices are deleted.
Practical examples:
- Automatically notify an external system when a new invoice is created.
- Sync product updates by listening to modification events.
- Track deletions of clients or documents to maintain data consistency across platforms.
Properties
| Name | Meaning |
|---|---|
| Company ID | The numeric identifier of the company for which the webhook will be created. |
| Sink | The URL endpoint where webhook event notifications will be sent. |
| Verified | Boolean flag indicating whether the webhook has been verified (true/false). |
| Types | The event types to subscribe to. Options: Created, Modified, Deleted. Multiple can be selected. |
Output
The node outputs JSON data representing the response from the Fatture in Cloud API after creating the webhook. This typically includes details about the newly created webhook such as its ID, status, subscribed event types, and other metadata.
If the operation fails, the output may contain an error object describing the issue.
The node does not output binary data.
Dependencies
- Requires an active connection to the Fatture in Cloud API using an OAuth2-based API key credential.
- The node depends on the internal WebhooksModule class that handles communication with the API.
- No additional environment variables are explicitly required beyond the configured API authentication.
Troubleshooting
Common issues:
- Invalid or missing Company ID: Ensure the company ID exists and is correct.
- Incorrect Sink URL: The webhook URL must be reachable and accept incoming POST requests.
- Permission errors: The API credentials must have permissions to create webhooks for the specified company.
- Event type selection: At least one event type should be selected; otherwise, the webhook may not function as expected.
Error messages:
Fatture in Cloud API Error: ...indicates an API-level failure. Check the detailed status and message for clues.- Validation errors often mention missing or invalid parameters.
- Network or authentication errors suggest checking API credentials and connectivity.
Resolution tips:
- Verify all input properties before execution.
- Confirm the sink URL is publicly accessible and correctly configured.
- Review API permissions and regenerate credentials if necessary.
- Use the "Continue On Fail" option to handle errors gracefully during batch executions.