Actions109
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Websites Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
- Users Actions
- Activity Logs Actions
- Articles Actions
Overview
The AvantGuard - Hudu node (Resource: Cards, Operation: Get Cards Lookup) allows you to look up card information from an external integration via the Hudu API. This is useful for scenarios where you need to retrieve card details based on identifiers from other systems, such as synchronizing data between Hudu and third-party platforms or automating workflows that require card metadata.
Practical examples:
- Fetching card details in Hudu using an integration slug and external IDs.
- Automating ticket enrichment by pulling related card info from Hudu based on external system references.
Properties
| Name | Type | Meaning |
|---|---|---|
| Integration Slug | String | Identifier of the external integration. Required to specify which integration to query. |
| Additional Query Parameters | Collection | Optional parameters to refine the lookup. Includes: |
| └─ Integration Id | String | ID in the external integration. Used if "Integration Identifier" is not set. |
| └─ Integration Identifier | String | Identifier in the external integration (used if "Integration Id" is not set). |
Output
The node outputs a json field containing the card lookup results returned by the Hudu API. The structure of this output will typically include card details relevant to the provided integration slug and identifiers. The exact fields depend on the Hudu API response but may include properties like card name, ID, status, and any associated metadata.
Dependencies
- External Service: Requires access to a Hudu instance with the appropriate API enabled.
- API Key/Credentials: Needs valid credentials (
avantguardHuduApi) configured in n8n, including the base URL and authentication token. - n8n Configuration: Ensure the credential named
avantguardHuduApiis set up in your n8n instance.
Troubleshooting
Missing Credentials:
Error: "No credentials found"
Resolution: Make sure theavantguardHuduApicredential is properly configured in n8n.Invalid Integration Slug or Identifiers:
Error: "Not Found" or empty results
Resolution: Double-check the values for "Integration Slug", "Integration Id", and "Integration Identifier". Ensure they match records in your Hudu instance.API Connection Issues:
Error: "Network Error" or "Failed to fetch"
Resolution: Verify the base URL in your credentials and ensure your n8n instance can reach the Hudu API endpoint.