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
This node allows you to create (post) export jobs in the "Exports" resource of the AvantGuard Hudu API. It is useful for automating the process of exporting data from Hudu, such as asset layouts or other resources, by programmatically triggering exports via n8n workflows.
Common scenarios:
- Automating regular exports of asset layouts for backup or reporting.
- Integrating Hudu export functionality into larger automation pipelines.
- Triggering exports based on events or schedules within n8n.
Example:
You could use this node to automatically export a set of asset layouts every week and then send the exported data to another system or store it in cloud storage.
Properties
| Name | Type | Meaning |
|---|---|---|
| Additional Body Fields | Collection | Optional fields to include in the request body. Lets you specify details for the export job. |
| └ Export | JSON | The main export configuration, e.g., which asset layout IDs to export. |
Output
The node outputs a json object containing the response from the Hudu API after creating an export job. The structure typically includes information about the created export, such as its ID, status, and any relevant metadata returned by the API.
Note: The exact output fields depend on the Hudu API's response for the "Post Exports" operation.
Dependencies
- External Service: Requires access to the AvantGuard Hudu API.
- API Key/Credentials: Needs valid credentials (
avantguardHuduApi) with appropriate permissions. - n8n Configuration: The base URL for the Hudu instance must be set in the credentials.
Troubleshooting
- Invalid Credentials: If the API key or base URL is incorrect, you may receive authentication errors. Double-check your credentials in n8n.
- Malformed Export JSON: If the "Export" field contains invalid JSON, the node may throw parsing errors. Ensure the JSON is properly formatted.
- Missing Required Fields: If required fields for the export are not provided, the API may return validation errors. Review the API documentation for required parameters.