EdgeOne Pages HTML Deploy icon

EdgeOne Pages HTML Deploy

Deploy HTML content to EdgeOne Pages and get shareable URLs
Join our community

Overview

This node, "EdgeOne Pages HTML Deploy," allows users to deploy custom HTML content to the EdgeOne Pages platform and receive shareable URLs in return. It is useful for scenarios where you want to quickly publish static HTML pages without managing your own hosting infrastructure. For example, you can use it to share landing pages, simple web presentations, or temporary HTML snippets with others via a URL.

Properties

Name Meaning
HTML Content The raw HTML code that you want to deploy to EdgeOne Pages. This is required input.

Output

The node outputs an array of JSON objects, each corresponding to one input item processed. Each output object contains:

  • key: A unique identifier key returned by the EdgeOne Pages service for the deployed HTML.
  • url: The shareable URL where the deployed HTML page can be accessed.
  • originalHtml: The original HTML content that was deployed.
  • timestamp: The ISO timestamp when the deployment occurred.

If the node encounters an error and is configured to continue on failure, the output will include an object with:

  • error: The error message describing what went wrong.
  • timestamp: The time when the error happened.

Dependencies

  • Requires internet access to send HTTP POST requests to the EdgeOne Pages API endpoint at https://mcp.edgeone.site/kv/set.
  • No explicit API keys or authentication tokens are used in this implementation; however, the request includes a fixed header "X-Installation-ID": "n8n".
  • The node depends on n8n's built-in HTTP request helper to perform the API call.

Troubleshooting

  • Missing HTML Content: If the "HTML Content" property is empty, the node throws an error indicating that HTML content is required. Ensure you provide valid HTML.
  • HTTP Request Failures: Network issues or API endpoint problems may cause the HTTP request to fail. Check your network connection and verify the EdgeOne Pages service status.
  • Unexpected API Response: If the response from the API does not contain expected fields (key and url), the node might throw an error. Confirm the API contract has not changed.
  • Continue On Fail Behavior: When enabled, errors for individual items do not stop the entire workflow but instead output error details per item.

Links and References

Discussion