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 to update a public photo record. Specifically, the "Update" operation on the "Public Photo" resource allows users to modify details of an existing public photo by specifying its ID and updating associated metadata such as the type of record it relates to and the record's ID.
Common scenarios for this node include:
- Updating the association of a public photo to a different article or record in your documentation system.
- Correcting metadata about a public photo after it has been uploaded.
- Automating updates to photo records as part of a larger workflow managing documentation assets.
For example, if you have a photo initially linked to one article but want to reassign it to another, this node can perform that update programmatically.
Properties
| Name | Meaning |
|---|---|
| Photo ID | The unique identifier (number) of the public photo to update. |
| Record Type | The updated type of record the photo is associated with, e.g., "Article". |
| Record ID | The ID (number) of the record the photo will be associated with after the update. |
Output
The node outputs JSON data representing the updated public photo record as returned by the Hudu API. Each output item corresponds to an input item processed and includes the updated fields reflecting the changes made.
If the node supports binary data output (not explicitly shown in the provided code), it would typically represent the photo file itself or related media content. However, based on the static analysis, the output focuses on JSON metadata about the public photo.
Dependencies
- Requires an active connection to the Hudu REST API.
- Needs an API key credential configured in n8n to authenticate requests.
- The base URL for the Hudu API must be set in the node credentials.
- No other external dependencies are indicated.
Troubleshooting
- Invalid Photo ID: If the specified Photo ID does not exist, the API will likely return an error indicating the photo was not found. Verify the ID before running the node.
- Authentication Errors: Missing or incorrect API key credentials will cause authentication failures. Ensure the API key is valid and properly configured.
- Invalid Record Type or Record ID: Providing a record type or ID that does not exist or is not supported may result in errors. Confirm these values correspond to valid records in Hudu.
- Network Issues: Connectivity problems to the Hudu API endpoint will cause request failures. Check network access and base URL configuration.
- Continue On Fail Behavior: If enabled, the node will continue processing subsequent items even if some fail, returning error messages in the output JSON.
Links and References
- Hudu API Documentation — Official API docs for reference on public photo endpoints and payloads.
- n8n Documentation — For general guidance on using credentials and configuring HTTP-based nodes.