Hudu icon

Hudu

Interact with Hudu REST API

Actions100

Overview

This node interacts with the "Procedure" resource of the Hudu REST API, specifically supporting the "Get Many" operation. It retrieves multiple procedure records from Hudu based on user-defined filters and pagination options.

Common scenarios for this node include:

  • Fetching a list of procedures to display or process in workflows.
  • Filtering procedures by company, template type, name, parent procedure, or URL slug.
  • Retrieving all procedures or limiting the number of results for performance or data volume control.

Practical example:

  • A user wants to get all procedures related to a specific company to generate reports or trigger follow-up actions.
  • Another use case is fetching only global templates or child procedures under a certain parent procedure for hierarchical processing.

Properties

Name Meaning
Return All Boolean option to return all matching procedures or limit the number of results returned.
Limit Maximum number of procedure records to return when "Return All" is false. Minimum value is 1.
Filters Collection of optional filters to narrow down the procedures retrieved:
- Company Name or ID Filter procedures by selecting a company from a list or specifying its ID via expression.
- Company Template Filter procedures that are company-specific templates by providing a numeric template ID.
- Global Template Boolean filter to specify whether to retrieve only global templates.
- Name Filter procedures by their name (string match).
- Parent Procedure ID Filter to get child procedures of a specific parent procedure by providing its numeric ID.
- Slug Filter procedures by their URL slug (string match).

Output

The node outputs an array of JSON objects representing the procedures retrieved from the Hudu API. Each object corresponds to one procedure and contains all relevant fields as returned by the API.

  • The output includes metadata about each procedure such as IDs, names, templates, parent relationships, slugs, and other procedure-specific details.
  • If the node encounters errors per item and "Continue On Fail" is enabled, it outputs error information in JSON format for those items.
  • No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Hudu REST API.
  • The base URL and API key must be configured in the node credentials.
  • The node relies on internal helper methods to call the Hudu API endpoints corresponding to procedures.
  • Option loaders are used to populate dropdowns for companies and other related entities.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Providing invalid filter values (e.g., non-numeric IDs) may result in API errors.
    • Requesting too many records without enabling pagination or limits might lead to timeouts or large payloads.

  • Error messages:

    • "The resource \"procedures\" is not known!" — indicates an unsupported resource was selected; ensure "Procedure" resource is chosen.
    • API errors returned from Hudu (e.g., 401 Unauthorized, 400 Bad Request) will be surfaced as node execution errors.

  • Resolutions:

    • Verify API credentials and permissions.
    • Use valid filter values and types.
    • Use "Return All" judiciously or set reasonable limits to avoid performance issues.
    • Enable "Continue On Fail" to handle partial failures gracefully.

Links and References

Discussion