Alegra (Unofficial - BETA) icon

Alegra (Unofficial - BETA)

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

Actions37

Overview

This node integrates with the Alegra API to update an existing estimate (quote) in your accounting or invoicing system. It allows you to modify details such as the estimate date, due date, internal observations, notes printed on the estimate, and its status.

Common scenarios where this node is useful include:

  • Adjusting the due date of a pending estimate after client negotiations.
  • Adding internal comments or annotations for team members.
  • Changing the status of an estimate to reflect its current state (e.g., from "Open" to "Accepted").
  • Updating dates to correct errors or reflect new timelines.

Practical example:

  • After sending a quote to a client, you realize the due date needs to be extended by a week. Using this node, you can update the due date without recreating the entire estimate.
  • Marking an estimate as "Invoiced" once it has been converted into an invoice.

Properties

Name Meaning
Estimate ID The unique identifier of the estimate you want to update.
Update Fields A collection of fields you want to update on the estimate:
- Date The new estimate date in YYYY-MM-DD format.
- Due Date The new due date for the estimate in YYYY-MM-DD format.
- Observations Internal observations or comments about the estimate (not visible to clients).
- Anotation Notes that will be printed on the estimate document sent to clients.
- Status The current status of the estimate. Options are: Open, Accepted, Rejected, Invoiced.

Output

The node outputs a JSON object representing the updated estimate as returned by the Alegra API. This typically includes all the estimate's properties after the update, such as its ID, dates, client info, items, status, and any notes or observations.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Alegra API via an API key credential configured in n8n.
  • The node uses HTTP requests authenticated with this API key to perform updates.
  • Ensure the API key has permissions to update estimates in the Alegra account.

Troubleshooting

  • Common issues:

    • Invalid or missing Estimate ID: The node requires a valid estimate identifier; ensure the ID exists in Alegra.
    • Incorrect date formats: Dates must be provided in YYYY-MM-DD format; otherwise, the API may reject the request.
    • Insufficient permissions: The API key used must have rights to update estimates.
    • Network or authentication errors: Check API key validity and network connectivity.

  • Error messages:

    • "Unknown error occurred": Generic failure, possibly due to network issues or invalid credentials.
    • API response errors indicating invalid fields or unauthorized access should be resolved by verifying input values and API key permissions.

Links and References

Discussion