AvantGuard - WebhookSite icon

AvantGuard - WebhookSite

AvantGuard - WebhookSite

Actions100

Overview

This node operation updates an existing company record by its unique ID. It is useful in scenarios where you need to modify company details such as name, address, contact information, or other metadata after the company has been created. For example, you might use this node to update a company's phone number or address when those details change.

Properties

Name Meaning
Id The unique identifier of the company to update (required).
Additional Body Fields Optional fields to update on the company, including:
- Name The name of the company.
- Nickname The nickname of the company.
- Company Type The type/category of the company.
- 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.
- State The state where the company is located.
- Zip The zip/postal code of the company's location.
- Country Name The country where the company is located.
- Phone Number The company's phone number.
- Fax Number The company's fax number.
- Website The company's website URL.
- Id Number The company's identification number.
- Parent Company Id The ID of the parent company, if applicable.
- Notes Additional notes about the company.

Output

The node outputs JSON data representing the updated company object returned from the API after the update operation. This typically includes all the company's current properties reflecting the changes made.

If the node supports binary data output, it would represent associated files or attachments related to the company, but based on the provided information, this operation focuses on JSON data only.

Dependencies

  • Requires an API key credential for authentication with the external service managing company data.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on an OpenAPI-based client library for making HTTP requests to the backend service.

Troubleshooting

  • Common issues:
    • Providing an invalid or non-existent company ID will result in errors indicating the company was not found.
    • Missing required authentication credentials will cause authorization failures.
    • Invalid field values (e.g., incorrect data types) in additional body fields may cause validation errors.
  • Error messages:
    • "Company not found" — Verify the company ID is correct and exists.
    • "Unauthorized" or "Authentication failed" — Check that the API key credential is correctly set up.
    • "Validation error" — Review the input fields for correct formats and required values.

Links and References

  • Refer to the API documentation of the external service managing companies for detailed field descriptions and constraints.
  • n8n documentation on how to configure API credentials and use collection-type input properties.

Discussion