Actions109
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Websites Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
- Users Actions
- Activity Logs Actions
- Articles Actions
Overview
This node allows you to update an existing Matcher by its ID in the AvantGuard Hudu system. It is useful when you need to modify details of a Matcher, such as changing associated company IDs or updating identifiers. Common scenarios include synchronizing Matcher data with external systems, correcting information, or automating updates as part of a workflow.
Example use cases:
- Automatically update a Matcher’s company association when a related record changes.
- Batch-update Matchers with new identifiers during a migration process.
- Integrate with other n8n nodes to keep Matcher data consistent across platforms.
Properties
| Name | Type | Meaning |
|---|---|---|
| Id | Number | The ID of the Matcher to update. This uniquely identifies which Matcher will be modified. |
| Additional Body Fields | Collection | Optional fields to update on the Matcher. Includes: |
| - Company Id | Number | The updated company ID for the Matcher. |
| - Potential Company Id | Number | The updated potential company ID for the Matcher. |
| - Sync Id | String | The updated sync ID for the Matcher. |
| - Identifier | String | The updated identifier for the Matcher. |
Output
The node returns the JSON response from the AvantGuard Hudu API after updating the Matcher. The structure typically includes the updated Matcher object, reflecting all changes made. The exact fields depend on the API's response but generally mirror the properties of a Matcher (such as id, company_id, potential_company_id, sync_id, identifier, etc.).
Example output:
{
"id": 123,
"company_id": 456,
"potential_company_id": 789,
"sync_id": "abc-123",
"identifier": "matcher-001",
// ...other Matcher fields
}
Dependencies
- External Service: Requires access to the AvantGuard Hudu API.
- API Credentials: You must configure the
avantguardHuduApicredential in n8n, including the base URL and authentication details. - n8n Configuration: Ensure that the credentials are set up and the node has network access to the Hudu API endpoint.
Troubleshooting
- Invalid or Missing ID: If the provided Matcher ID does not exist, the API may return a "not found" error. Double-check the ID value.
- Authentication Errors: If credentials are missing or incorrect, you may see errors like "401 Unauthorized." Verify your API key and base URL.
- Validation Errors: If required fields are missing or have invalid values, the API may return descriptive error messages. Review the input property values.
- Network Issues: Timeouts or connection errors can occur if the API is unreachable. Ensure network connectivity and correct base URL configuration.