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 Hudu REST API, specifically providing functionality to look up "cards" within Hudu's system. The "Card Lookup" operation allows users to retrieve card data from various external integrations connected through Hudu. This is useful in scenarios where you want to fetch detailed information about a specific card linked to an external service integration, such as Office 365, Autotask, or Ninja, among others.
Practical examples include:
- Retrieving ticket or asset details from an external IT management system integrated into Hudu.
- Fetching user or device cards from cloud services like Office 365 or Cloudflare.
- Looking up configuration or monitoring cards from RMM tools like Pulseway or Datto.
This operation helps automate workflows that require fetching and processing card data from multiple integrated platforms via Hudu.
Properties
| Name | Meaning |
|---|---|
| Integration Slug | The type of external integration to use for the lookup. Options include: Office 365, Autotask, Cw Manage, Bms, Syncro, Domotz, Quickpass, Cloudradial, Auvik, Liongard, Ninja, Dattormm, Atera, Nsight, Halo, Pulseway Rmm, Repairshopr, Datto, Watchman, Mapbox, Openai, Superops, Unifi, Ncentral, Meraki, Addigy, Cloudflare, Level. |
| Additional Fields | Optional additional parameters to refine the lookup: |
| - Integration ID | The ID of the card in the external integration. Must be provided unless Integration Identifier is set. |
| - Integration Identifier | An alternative identifier in the external integration used if Integration ID is not set. |
Output
The output is a JSON array containing the card data retrieved from the specified external integration via Hudu. Each item corresponds to a card matching the lookup criteria. The structure of each JSON object depends on the external integration's card schema but generally includes fields representing the card's attributes and metadata.
If the node supports binary data output (not explicitly shown in the code), it would typically represent attachments or files related to the card, but this is not indicated in the provided source.
Dependencies
- Requires an active connection to the Hudu REST API.
- Needs an API key credential configured in n8n for authentication with Hudu.
- The base URL for the Hudu API must be set in the node credentials.
- The node relies on Hudu's external integrations being properly configured to perform lookups.
Troubleshooting
Common Issues:
- Missing or incorrect API key or base URL in credentials will cause authentication failures.
- Providing neither Integration ID nor Integration Identifier will result in incomplete lookup parameters.
- Selecting an unsupported integration slug or a typo in the slug may cause errors or empty results.
- Network connectivity issues can prevent successful API calls.
Error Messages:
"The resource \"cards\" is not known!"— indicates the resource parameter was not correctly set to "cards".- API errors returned by Hudu (e.g., 401 Unauthorized, 404 Not Found) should be checked for correct credentials and valid identifiers.
- If
continueOnFailis disabled, any error will stop execution; enabling it allows the workflow to continue despite individual item errors.
Links and References
- Hudu API Documentation — official API docs for understanding card data and integrations.
- n8n Documentation — for configuring credentials and using custom nodes.
- External integration documentation (e.g., Office 365, Autotask) for understanding identifiers and IDs used in lookups.