Actions100
- Activity Log Actions
- Article Actions
- Asset Actions
- Asset Layout Actions
- Asset Layout Field Actions
- Asset Password Actions
- Card Actions
- Company Actions
- Expiration Actions
- Folder Actions
- IP Address Actions
- List Actions
- Magic Dash Actions
- Matcher Actions
- Network Actions
- Password Folder Actions
- Procedure Actions
- Procedure Task Actions
- Public Photo Actions
- Rack Storage Actions
- Rack Storage Item Actions
Overview
This node interacts with the Magic Dash resource of the Hudu API, specifically supporting the "Get Many" operation. It allows users to retrieve multiple Magic Dash entries from their Hudu account, optionally filtered by company or title, and control how many results are returned.
Common scenarios where this node is beneficial include:
- Fetching a list of Magic Dash dashboards for reporting or monitoring purposes.
- Integrating Magic Dash data into workflows that require bulk retrieval of dashboard information.
- Filtering dashboards by company or title to automate targeted processing or notifications.
For example, a user might want to get all Magic Dash dashboards related to a specific company or only those whose titles contain certain keywords, then use that data downstream in their automation.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all matching Magic Dash results or limit the number of results returned. |
| Limit | The maximum number of Magic Dash results to return if "Return All" is set to false (minimum 1). |
| Filters | Collection of filters to narrow down the Magic Dash results: |
| Company Name or ID | Select a company by name or specify its ID to filter Magic Dash dashboards belonging to that company. |
| Title | Filter Magic Dash dashboards by their title (string match). |
Output
The node outputs an array of JSON objects representing Magic Dash dashboards retrieved from the Hudu API. Each object corresponds to one Magic Dash entry and contains its properties as returned by the API.
The output includes a json field with the dashboard data. If multiple input items are processed, each output item is paired with its corresponding input item index.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Hudu REST API via an API key credential configured in n8n.
- The base URL and API key must be set in the node credentials to authenticate requests.
- The node relies on internal utility functions to handle API calls and pagination when fetching multiple results.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Specifying invalid company IDs or titles in filters may result in empty responses.
- Setting a very high limit without enabling "Return All" may truncate results unexpectedly.
Error messages:
"The resource \"magic_dash\" is not known!"— This indicates the resource parameter was not correctly set to "magic_dash".- API errors such as unauthorized access or rate limiting will propagate from the Hudu API and should be checked against your API key permissions and usage limits.
Resolutions:
- Verify API credentials and ensure they have sufficient permissions.
- Double-check filter values for correctness.
- Use "Return All" option if you need to fetch all available results beyond the default limit.
Links and References
- Hudu API Documentation — Official API docs for understanding Magic Dash endpoints and parameters.
- n8n Expressions — Guide on using expressions to dynamically set property values like company IDs.