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 interacts with the Fatture in Cloud API to manage webhook subscriptions for a company. Specifically, the Webhook - Update operation allows users to modify an existing webhook subscription by updating its URL endpoint (sink), verification status, and subscribed event types. This is useful when you need to change where webhook notifications are sent or adjust which events trigger those notifications.
Common scenarios include:
- Changing the destination URL of a webhook after migrating services.
- Updating the types of events your application listens to without creating a new webhook.
- Marking a webhook as verified after confirming ownership of the endpoint.
Example: You have a webhook that notifies your system about invoice creations. You want to update it to also receive notifications on invoice modifications and deletions, and confirm the webhook is verified.
Properties
| Name | Meaning |
|---|---|
| Company ID | The numeric identifier of the company for which the webhook subscription belongs. |
| Subscription ID | The unique string ID of the webhook subscription to update. |
| Sink | The URL endpoint where webhook notifications will be sent. |
| Verified | Boolean flag indicating whether the webhook has been verified. |
| Types | The event types to subscribe to; options are: Created, Modified, Deleted. |
Output
The node outputs JSON data representing the updated webhook subscription details returned from the Fatture in Cloud API. This typically includes confirmation of the updated fields such as the subscription ID, sink URL, verification status, and subscribed event types.
No binary data output is involved in this operation.
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 to perform the API call.
- Proper configuration of the company context via the Company ID is necessary.
- Network access to the Fatture in Cloud API endpoints must be available.
Troubleshooting
- Common issues:
- Invalid or missing Company ID or Subscription ID can cause errors.
- Incorrect sink URL format may lead to webhook verification failures.
- Insufficient permissions or expired API credentials will result in authorization errors.
- Error messages:
"Unknown resource: webhook"indicates the resource parameter was not set correctly."Fatture in Cloud API Error: <message>"shows an error response from the API; check the message and status code for details.
- Resolutions:
- Verify all required parameters are provided and valid.
- Ensure the sink URL is reachable and properly formatted.
- Refresh or reconfigure API credentials if authentication fails.
- Use the "continue on fail" option to handle partial failures gracefully.
Links and References
- Fatture in Cloud API Documentation (official API docs)
- n8n documentation on creating and managing webhooks (for general webhook concepts)