AvantGuard - HuduInstall

Overview

The AvantGuard - Hudu node for n8n allows you to interact with the Hudu API, specifically to retrieve a list of "Matchers" associated with a given integration. The "Get Matchers" operation is useful for scenarios where you need to fetch and filter matcher records—such as synchronizing company data, auditing integration matches, or automating workflows based on match status.

Practical examples:

• Retrieve all matchers for a specific integration to review which companies have been matched.
• Filter matchers by company ID or match status to trigger downstream automation.
• Paginate through large sets of matcher results for reporting or further processing.

Properties

Name	Type	Meaning
Integration Id	Number	The ID of the integration (found in the URL when editing an integration). Required.
Additional Query Parameters	Object	Optional collection of filters and pagination options:
└─ Matched	Boolean	Filter by whether the company has already been matched.
└─ Sync Id	Number	Filter by the ID of the record in the integration (if integration's ID is an integer).
└─ Identifier	String	Filter by the identifier in the integration (if integration's ID is a string).
└─ Page	Number	The current page of results (for pagination).
└─ Page Size	Number	The number of results to return per page.
└─ Company Id	Number	Filter by company ID.

Output

The node outputs a JSON array of matcher objects retrieved from the Hudu API. Each object typically contains details about a matcher, such as IDs, match status, and related metadata. The exact structure depends on the Hudu API response, but users can expect fields relevant to the matchers resource.

Example output:

[
  {
    "id": 123,
    "integration_id": 456,
    "company_id": 789,
    "matched": true,
    "sync_id": 1011,
    "identifier": "abc-123",
    // ...other matcher fields
  }
]

Note: The node does not output binary data.

Dependencies

• External Service: Requires access to the Hudu API.
• API Key/Credentials: Needs valid avantguardHuduApi credentials configured in n8n, including the base URL (baseUrl) for your Hudu instance.
• n8n Configuration: Ensure the credentials are set up in n8n under the name avantguardHuduApi.

Troubleshooting

Common Issues:

• Invalid Credentials: If the API key or base URL is incorrect, authentication errors will occur. Double-check your credential setup.
• Missing Required Property: The "Integration Id" is required. Omitting it will result in validation errors.
• API Rate Limits or Errors: If too many requests are made, the Hudu API may throttle or reject requests. Check API documentation for rate limits.
• Incorrect Query Parameters: Supplying invalid values (e.g., non-existent company ID) may result in empty responses or API errors.

Error Messages & Resolutions:

• 401 Unauthorized: Verify your API credentials and permissions.
• 400 Bad Request: Check that all required parameters are provided and correctly formatted.
• 404 Not Found: Ensure the specified integration or company exists.

Links and References

• Hudu API Documentation
• n8n Documentation: Custom Nodes
• AvantGuard GitHub