Actions144
- Activity Log Actions
- API Info Actions
- Article Actions
- Asset Actions
- Asset Layout Actions
- Asset Layout Field Actions
- Asset Password Actions
- Card Actions
- Company Actions
- Expiration Actions
- Export Actions
- Folder Actions
- Group Actions
- IP Address Actions
- List Actions
- List Options Actions
- Magic Dash Actions
- Matcher Actions
- Network Actions
- Password Folder Actions
- Photo Actions
- Procedure Actions
- Procedure Task Actions
- Public Photo Actions
- Rack Storage Actions
- Rack Storage Item Actions
- Relation Actions
- S3 Export Actions
- Upload Actions
- User Actions
- VLAN Actions
- VLAN Zone Actions
- Website Actions
Card → Jump
AI-generatedOverview
The node performs a 'Jump' operation on a 'Card' resource within the Hudu system. This operation allows users to interact with external integrations by specifying an integration slug and type, and optionally providing an integration ID or identifier. It is useful for scenarios where users need to link or jump to specific entities in various external integrations directly from Hudu cards, facilitating seamless cross-platform navigation and management.
Use Case Examples
- Jump to a specific entity in the Autotask integration by providing the integration slug 'autotask' and the relevant integration type and ID.
- Use the node to jump to a contact or asset in the Office 365 integration by specifying the integration slug 'office_365' and the appropriate integration type and identifier.
Properties
| Name | Meaning |
|---|---|
| Integration Slug | The integration type to use, such as office_365, autotask, cw_manage, etc. This determines which external integration the jump operation targets. |
| Integration Type | Type of card. Specifies the type of entity within the integration to jump to. Users may need to contact support for a list of valid types for specific integrations. |
| Additional Fields | Optional additional fields to specify the target entity in the external integration. Includes Integration ID or Integration Identifier, where at least one must be provided to identify the entity to jump to. |
Output
JSON
items- Array of results from the jump operation, each item paired with the input item index.
Dependencies
- Hudu REST API
- An API key credential for Hudu
Troubleshooting
- Ensure that either Integration ID or Integration Identifier is provided; otherwise, the operation will fail due to missing target entity information.
- Verify that the Integration Slug and Integration Type are correctly set to match the external integration and entity type.
- If the resource or operation is not recognized, the node will throw an error indicating the unknown resource.
- Check API credentials and network connectivity to the Hudu API to avoid authentication or communication errors.