Fatture in Cloud icon

Fatture in Cloud

Interact with Fatture in Cloud API

Overview

This node interacts with the Fatture in Cloud API, specifically managing webhook subscriptions when the "Webhook" resource is selected. The "Delete" operation under the Webhook resource allows users to remove an existing webhook subscription from their Fatture in Cloud account. This is useful for cleaning up or disabling webhooks that are no longer needed, preventing unnecessary callbacks or notifications.

Practical examples include:

  • Removing a webhook subscription after a project or integration is completed.
  • Deleting outdated or incorrect webhook subscriptions to avoid receiving irrelevant event data.
  • Managing webhook lifecycle programmatically as part of automation workflows.

Properties

Name Meaning
Company ID The numeric identifier of the company within Fatture in Cloud where the webhook exists.
Subscription ID The string identifier of the specific webhook subscription to delete.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will be a confirmation object indicating success or details about the deletion. If the operation fails, error information is returned instead.

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 Webhooks module of the Fatture in Cloud integration.
  • Proper configuration of the API credentials in n8n is necessary to authenticate requests.

Troubleshooting

  • Common issues:

    • Invalid or missing Company ID or Subscription ID parameters will cause the API call to fail.
    • Expired or invalid API authentication tokens will prevent successful communication with the Fatture in Cloud API.
    • Attempting to delete a non-existent webhook subscription will result in an error response.
  • Error messages and resolutions:

    • "Fatture in Cloud API Error: [message]": Indicates an issue reported by the API. Check the message details for specifics such as invalid IDs or permission issues.
    • Status codes like 401 or 403: Suggest authentication or authorization problems; verify API credentials and permissions.
    • Validation errors: Ensure all required fields (Company ID and Subscription ID) are correctly provided and formatted.
  • Enabling "Continue On Fail" in the node settings can help handle errors gracefully within workflows.

Links and References

Discussion