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 "Send by Email" operation allows users to send an existing estimate via email to a specified recipient. This is useful in scenarios where you want to automate sending quotes to clients directly from your workflow without manual intervention.

For example, after creating or updating an estimate in Alegra, you can use this node to automatically email the estimate to the client and optionally send a copy to yourself for record-keeping.

Properties

Name Meaning
Estimate ID The unique identifier of the estimate you want to send by email.
To The email address of the recipient who will receive the estimate.
Send Copy to Myself Boolean flag indicating whether to send a copy of the estimate email to yourself.

Output

The output JSON contains the response from the Alegra API after attempting to send the estimate email. It typically includes confirmation details about the email dispatch status.

No binary data is output by this operation.

Example output structure:

{
  "success": true,
  "message": "Email sent successfully"
}

(Note: Actual response fields depend on Alegra API's email endpoint.)

Dependencies

  • Requires an active Alegra API credential configured in n8n with appropriate permissions.
  • The node makes authenticated HTTP POST requests to the /estimates/{id}/email endpoint of the Alegra API.
  • No additional external dependencies are required.

Troubleshooting

  • Common issues:

    • Invalid or missing Estimate ID: Ensure the provided estimate ID exists in Alegra.
    • Invalid email address format in the "To" field.
    • API authentication errors due to incorrect or expired credentials.
    • Network connectivity issues preventing access to Alegra API.
  • Error messages:

    • "Unknown error occurred": Generic catch-all; check network and API credentials.
    • API errors returned by Alegra (e.g., 404 if estimate not found, 400 for bad request) will be surfaced as node execution errors.
  • Resolution tips:

    • Verify the estimate ID is correct and the estimate exists.
    • Confirm the email address is valid.
    • Check that the API key credential is correctly set up and has necessary permissions.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.

Links and References

Discussion