Alegra (Unofficial - BETA) icon

Alegra (Unofficial - BETA)

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

Actions37

Overview

The node integrates with the Alegra API to manage tax records. Specifically, the "Tax - Create" operation allows users to create a new tax entry in Alegra by specifying its name, percentage rate, type, and optional additional details such as description and status.

This node is beneficial for automating tax setup in accounting workflows, ensuring consistent tax configurations across invoices, payments, and other financial documents managed via Alegra. For example, a business can automatically add new tax rates when launching products in different regions or update retention taxes without manual intervention.

Properties

Name Meaning
Name The name of the tax (e.g., "VAT", "Sales Tax").
Percentage The tax rate as a percentage (supports two decimal places).
Type The category of the tax. Options: General Tax, Retention, Compound Tax.
Additional Fields Optional extra fields:
- Description A textual description of the tax.
- Status Boolean indicating if the tax is active (true) or inactive (false).

Output

The output JSON contains the full response from the Alegra API after creating the tax. This typically includes the newly created tax's unique identifier, name, percentage, type, status, description, and any other metadata returned by Alegra.

No binary data is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Alegra API.
  • The node uses HTTP requests to the Alegra API endpoints under the configured environment URL.
  • Proper network connectivity to Alegra's API service is necessary.

Troubleshooting

  • Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Validation errors: Missing required fields like "Name", "Percentage", or "Type" will cause the API to reject the request. Double-check input values.
  • API connectivity issues: Network problems or incorrect environment URLs can cause request failures.
  • Unexpected errors: The node throws error messages from the API or generic errors; enabling "Continue On Fail" can help handle these gracefully in workflows.

Links and References

Discussion