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 contact information. It allows users to modify details of an existing contact such as name, email, phone numbers, address, and additional observations. This is useful in scenarios where contact data needs to be kept current, for example, updating client or provider records after changes in their details.

Practical examples include:

  • Updating a client's email and phone number after they provide new contact info.
  • Modifying the address of a supplier to reflect a recent relocation.
  • Adding notes or observations about a contact for internal reference.

Properties

Name Meaning
Contact ID The unique identifier of the contact to update.
Update Fields Collection of fields to update on the contact:
- Name: Contact's full name.
- Email: Contact's email address.
- Phone Primary: Primary phone number.
- Phone Secondary: Secondary phone number.
- Mobile: Mobile phone number.
- Fax: Fax number.
- Address: Structured address including street address, city, department/state, country, postal/ZIP code.
- Observations: Additional notes or comments about the contact.

Output

The node outputs JSON data representing the updated contact object returned by the Alegra API. This typically includes all contact fields after the update has been applied, reflecting the current state of the contact record.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Alegra API.
  • The node uses the Alegra API endpoint configured via the credential environment.
  • Network connectivity to the Alegra API service is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Contact ID will cause the update to fail.
    • Providing invalid field values (e.g., malformed email) may result in API errors.
    • Network or authentication failures can prevent successful updates.

  • Error messages:

    • Errors from the API are surfaced as node operation errors with descriptive messages.
    • "Unknown error occurred" indicates unexpected issues, possibly network or server-side problems.

  • Resolutions:

    • Verify that the Contact ID exists and is correct.
    • Ensure all input fields conform to expected formats.
    • Check API credentials and network connectivity.
    • Use the node’s "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion