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 focusing on the "Card" resource and its "Jump" operation. The "Jump" operation allows users to navigate or link directly to an entity within an external integration system from a Hudu card. This is useful for workflows where you want to quickly access or reference related data in third-party systems integrated with Hudu.
Practical scenarios include:
- Jumping to a ticket or asset in an external IT management system (e.g., Autotask, CW Manage) directly from a Hudu card.
- Linking to a user or company record in a CRM or RMM tool.
- Quickly accessing detailed information in various supported integrations without manual searching.
Properties
| Name | Meaning |
|---|---|
| Integration Slug | The type of external integration to use. 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. |
| Integration ID | The unique identifier of the integration instance to use. |
| Integration Type | The type/category of the integration (string). |
| Additional Fields | Optional additional parameters: |
| - Integration ID | ID of the entity in the external integration (alternative to main Integration ID). |
| - Integration Identifier | Identifier of the entity in the external integration if Integration ID is not set. |
Output
The node outputs JSON data representing the result of the jump operation. Each output item corresponds to an input item processed and includes the relevant data returned by the Hudu API for the jump action on the specified card.
- The
jsonoutput field contains the response data from the API call related to the jump operation. - If errors occur and "Continue On Fail" is enabled, error messages are output as JSON objects with an
errorproperty describing the issue. - No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Hudu REST API via an API key credential.
- The base URL and API key must be configured in the node credentials.
- The node depends on the availability and correct configuration of the external integrations referenced by the integration slug, ID, and type.
Troubleshooting
Common Issues:
- Incorrect or missing integration slug, ID, or type can cause the jump operation to fail.
- Network or authentication issues with the Hudu API will prevent successful execution.
- Providing invalid or incomplete additional fields may lead to errors.
Error Messages:
"The resource \"cards\" is not known!"— indicates the resource parameter was incorrect or unsupported.- API errors returned from Hudu will be passed through; check the message for details such as invalid credentials or missing permissions.
Resolutions:
- Verify all required properties are correctly set.
- Ensure the API key credential is valid and has necessary permissions.
- Confirm that the integration slug and IDs correspond to existing configured integrations in Hudu.
- Enable "Continue On Fail" to handle errors gracefully during batch processing.
Links and References
- Hudu API Documentation (for detailed API endpoints and integration setup)
- n8n Documentation on Creating Custom Nodes