Overview
This node integrates with the AnyWebsites HTML hosting service, allowing users to manage HTML content programmatically. Specifically, the "Update Content" operation lets users modify existing HTML pages hosted on AnyWebsites by updating their title, description, HTML content, visibility (public or private), access code for private content, and optional expiration date.
Common scenarios include:
- Updating a published webpage's content without needing to manually log into the hosting platform.
- Changing access permissions or expiration dates for time-sensitive content.
- Automating website content updates as part of a larger workflow, such as CMS publishing pipelines or marketing campaigns.
Example: A user can update an event landing page's HTML to reflect new details and set it to expire after the event date automatically.
Properties
| Name | Meaning |
|---|---|
| Title | The new title for the HTML content. |
| Description | Optional updated description for the content. |
| HTML Content | The updated HTML markup to replace the existing content. |
| Is Public | Whether the content should be publicly accessible (true) or restricted (false). |
| Access Code | Access code required to view the content if it is private (only shown if Is Public is false). |
| Expires At | Optional expiration date/time when the content will no longer be accessible. |
| Content ID | The unique identifier of the content to update (required to specify which content to modify). |
Output
The output JSON contains the updated content details returned from the AnyWebsites API. Key fields include:
content: An object representing the updated content metadata and properties.published_url: A full URL where the updated HTML content can be accessed publicly or privately depending on settings.
If the update is successful, the node outputs the updated content information including the new published URL constructed from the base URL of the AnyWebsites service combined with the content ID.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the AnyWebsites service.
- The node uses the AnyWebsites API endpoints to perform content updates.
- The base URL of the AnyWebsites service is retrieved from the stored credentials and used to construct the published URL.
Troubleshooting
Error: "The operation 'update' is not supported!"
This indicates an invalid operation parameter was passed. Ensure the operation is set exactly to "update".API request failures (e.g., 401 Unauthorized, 404 Not Found)
Check that the API key credential is valid and has permission to update the specified content ID. Verify the content ID exists.Missing required parameters
ThecontentIdandhtmlContentare mandatory. Omitting these will cause errors.Access code issues
If setting content to private (Is Public= false), ensure an access code is provided; otherwise, access may be blocked.Expiration date format
TheExpires Atproperty must be a valid datetime string. Invalid formats may cause API rejection.
Using the node’s "Continue On Fail" option can help handle individual item errors gracefully in batch operations.
Links and References
- AnyWebsites API Documentation (replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- General info on HTML Hosting Services