Hudu icon

Hudu

Interact with Hudu REST API

Matcher → Get Many

AI-generated

Overview

This node operation retrieves multiple matcher records from the Hudu integration based on specified filters and parameters. It is useful for scenarios where you need to fetch a list of matchers associated with a particular integration, optionally filtered by company, identifier, matched status, or sync ID. For example, you might use this to get all matchers for an integration to analyze or process them further in your workflow.

Use Case Examples

  1. Fetch all matchers for a given integration ID.
  2. Retrieve a limited number of matchers filtered by company name or ID.
  3. Get matchers that have already been matched for synchronization purposes.

Properties

Name Meaning
Integration ID The ID of the integration to fetch matchers from, required to identify the integration context.
Return All Whether to return all matcher results or limit the number of results.
Limit Maximum number of matcher results to return when 'Return All' is false.
Wrap Results in Single Item Whether to return all matcher results as a single item containing an 'items' array and a 'count' field, useful to prevent downstream nodes from executing once per result item.
Filters Optional filters to narrow down matcher results by company (name or ID), identifier, matched status, or sync ID.

Output

JSON

  • items - Array of matcher records returned when results are wrapped in a single item.
  • count - Count of matcher records returned when results are wrapped in a single item.
    - Individual properties of each matcher record returned as separate JSON objects when results are not wrapped.

Dependencies

  • Requires Hudu API credentials for authentication.

Troubleshooting

  • Common issues include invalid or missing Integration ID, which will prevent fetching matchers.
  • If filters are incorrectly specified, the node may return no results or unexpected results.
  • Enabling 'Wrap Results in Single Item' helps avoid rate limiting issues by reducing downstream executions.
  • Errors related to unknown resources or operations indicate misconfiguration of the node parameters.

Discussion