AnyWebsites

Overview

This node integrates with the AnyWebsites HTML hosting service, allowing users to manage HTML content programmatically. It supports operations such as uploading new HTML content, retrieving lists of uploaded content, fetching details of specific content, updating existing content, and deleting content.

A common use case is automating website content management workflows, for example:

• Automatically publishing HTML pages generated from other data sources.
• Managing a collection of hosted HTML snippets or landing pages.
• Cleaning up outdated or unwanted content by deleting it via automation.

The Delete Content operation specifically allows users to remove previously uploaded HTML content by specifying its unique content ID.

Properties

(Note: For the Delete Content operation, only the "Content ID" property is relevant.)

Output

The output JSON structure depends on the operation performed. For the Delete Content operation, the node returns the response from the API after attempting to delete the specified content. This typically includes confirmation of deletion or an error message if the content could not be deleted.

The output is structured as:

{
  "json": {
    // API response confirming deletion or error details
  },
  "pairedItem": {
    "item": <index_of_input_item>
  }
}

No binary data is produced by this node.

Dependencies

• Requires an API key credential for authenticating with the AnyWebsites service.
• The node uses an HTTP request helper function (anyWebsitesApiRequest) to communicate with the AnyWebsites API endpoints.
• Proper configuration of the API base URL and authentication credentials in n8n is necessary.

Troubleshooting

• Common issues:

  • Providing an invalid or non-existent Content ID will result in an error from the API indicating that the content was not found.
  • Missing or incorrect API credentials will cause authentication failures.
  • Network connectivity problems can prevent successful API calls.

• Error messages:

  • "The operation \"delete\" is not supported!" — This indicates an unsupported operation was requested; ensure the operation parameter is set correctly.
  • API errors returned from the AnyWebsites service (e.g., 404 Not Found) will be passed through and should be checked for correct Content ID usage.

• Resolution tips:

  • Verify the Content ID is correct and corresponds to existing content.
  • Check that the API key credential is valid and has sufficient permissions.
  • Enable "Continue On Fail" in the node settings to handle errors gracefully during batch processing.

Links and References

• AnyWebsites API Documentation (Replace with actual URL if available)
• n8n documentation on Creating Custom Nodes