Hudu icon

Hudu

Interact with Hudu REST API

Overview

This node interacts with the "Company" resource of an external system via its REST API, specifically supporting the Update operation for companies. It allows users to update various details of a company by specifying the company ID and the fields to modify.

Typical use cases include:

  • Automating updates to company records in bulk workflows.
  • Synchronizing company data from other systems or databases.
  • Correcting or enriching company information such as address, contact details, or company type.

For example, you could update a company's phone number and website after receiving new information from a CRM system, ensuring your records stay current without manual intervention.

Properties

Name Meaning
Company ID The unique numeric identifier of the company to update (required).
Update Fields A collection of fields to update on the company record. Options include:
- Address Line 1 The first line of the company's address.
- Address Line 2 The second line of the company's address.
- City The city where the company is located.
- Company Type The type/category of the company.
- Country Name The country where the company is located.
- Fax Number The company's fax number.
- ID Number The company's identification number.
- Name The official name of the company.
- Nickname A nickname or short name for the company.
- Notes Additional notes or comments about the company.
- Parent Company Name or ID Reference to a parent company, selectable from a list or specified by ID expression.
- Phone Number The company's phone number.
- State The state or region where the company is located.
- Website The company's website URL.
- ZIP The postal/ZIP code of the company's location.

Output

The node outputs JSON data representing the updated company record(s) returned from the API after the update operation. Each output item corresponds to one input item processed and includes the updated company details.

If the API supports it, the output may contain all fields of the company, reflecting the new state after the update.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the external system's REST API.
  • The base URL for the API must be set in the node credentials.
  • The node depends on internal helper methods to handle the HTTP request and response parsing.

Troubleshooting

  • Common issues:

    • Invalid or missing Company ID will cause the update to fail.
    • Providing no fields in "Update Fields" may result in no changes or an error.
    • Network or authentication errors if the API key or base URL is incorrect.
    • Selecting a non-existent parent company ID may cause validation errors.
  • Error messages:

    • "The resource "companies" is not known!" — indicates an invalid resource parameter; ensure "companies" is selected.
    • API errors returned from the server will be passed through; check the message for details like "Company not found" or "Invalid field".
  • Resolutions:

    • Verify that the Company ID exists in the target system.
    • Ensure at least one field is provided to update.
    • Confirm API credentials and endpoint configuration.
    • Use expressions carefully when specifying parent company IDs.

Links and References

  • n8n Expressions Documentation — for using expressions in property values.
  • Refer to the external system's API documentation for detailed information on company fields and update constraints (link not provided in source).

Discussion