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 → Lookup
AI-generatedOverview
This node interacts with the Hudu REST API to perform a lookup operation on the 'Card' resource. It allows users to retrieve card information from various external integrations by specifying the integration type and either an integration ID or an integration identifier. This is useful for scenarios where you need to fetch card data from different integrated systems within a workflow, such as retrieving customer or asset cards from platforms like Office 365, Autotask, or Ninja.
Use Case Examples
- Lookup a card in the Office 365 integration by providing the integration slug and integration ID.
- Retrieve a card from the Ninja integration using the integration identifier.
Properties
| Name | Meaning |
|---|---|
| Integration Slug | The integration type to use for the lookup (e.g., office_365, autotask, ninja). This determines which external system the card data will be fetched from. |
| Additional Fields | Optional fields to specify either the Integration ID or the Integration Identifier for the card lookup. One of these must be provided to identify the card in the external integration. |
Output
JSON
id- The unique identifier of the card in Hudu.name- The name of the card.integration_slug- The integration type used for the lookup.integration_id- The ID of the card in the external integration.integration_identifier- The identifier of the card in the external integration.details- Additional details or metadata about the card retrieved from the external integration.
Dependencies
- Hudu REST API
- An API key credential for Hudu
Troubleshooting
- Ensure that either Integration ID or Integration Identifier is provided; otherwise, the lookup will fail.
- Verify that the selected Integration Slug matches the external system where the card exists.
- Check API credentials and permissions to ensure access to the Hudu API and the external integrations.
- Common error messages may include 'The resource "cards" is not known!' if the resource parameter is incorrect, or authentication errors if API credentials are invalid.