Alegra (Unofficial - BETA) icon

Alegra (Unofficial - BETA)

Consume Alegra API - UNOFFICIAL BETA community node. NOT officially supported by Alegra.

Overview

This node integrates with the Alegra API to manage estimates (quotes). Specifically, the "Delete" operation for the "Estimate" resource allows users to delete an existing estimate by its ID. This is useful in scenarios where a quote is no longer valid or was created in error and needs to be removed from the Alegra system.

Practical examples:

  • Automatically deleting outdated or canceled quotes as part of a workflow.
  • Cleaning up test or draft estimates during data synchronization.
  • Removing duplicate or erroneous estimates programmatically.

Properties

Name Meaning
Estimate ID The unique identifier of the estimate to delete

Output

The output JSON contains the response from the Alegra API after attempting to delete the specified estimate. Typically, this will be an empty object or confirmation message indicating successful deletion. If the deletion fails, the output may contain an error message.

No binary data is output by this operation.

Dependencies

  • Requires an active connection to the Alegra API via an API key credential configured in n8n.
  • The node uses HTTP DELETE requests to the /estimates/{id} endpoint of the Alegra API.
  • Proper permissions on the API key are necessary to perform delete operations on estimates.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Estimate ID will result in an error from the API.
    • Network connectivity problems can cause request failures.
    • Insufficient API permissions will prevent deletion.
  • Error messages:

    • "Unknown error occurred": General failure, check network and API credentials.
    • API-specific errors such as "Estimate not found" indicate the provided ID does not exist.
  • Resolutions:

    • Verify the Estimate ID is correct and exists in Alegra.
    • Ensure the API key has delete permissions.
    • Check network connectivity and retry.
    • Enable "Continue On Fail" in the node settings if you want the workflow to proceed despite errors.

Links and References

Discussion