Extensions/Happy Horse by Ace Data Cloud
ComfyUI Extension

Happy Horse by Ace Data Cloud

Happy Horse video generation, editing, task lookup, and native video loading through Ace Data Cloud

By AceDataCloud·Created 21 days ago·Updated 14 days ago· 0
AceDataCloud/HappyHorseComfyUI
Nodes7
On cloudLocal install
CategoryAce Data Cloud/Happy Horse
Stars0
Updated14 days ago
Readme

Happy Horse for ComfyUI by Ace Data Cloud

Generate and edit Happy Horse (HappyHorse) videos with your Ace Data Cloud account, retrieve the same task ID, and load completed results as ComfyUI's native VIDEO type. These nodes call a hosted API; no local model or GPU is needed. Submissions consume Credits at the current Happy Horse price.

简体中文 · Ace Data Cloud · Issues

| Node | Dify action and model family | | --- | --- | | Happy Horse Text to Video | generate; 1.0 and 1.1 T2V | | Happy Horse Image to Video | image_to_video; 1.0 and 1.1 I2V | | Happy Horse Reference to Video | reference_to_video; 1.0 and 1.1 R2V | | Happy Horse Video Edit | video_edit; happyhorse-1.0-video-edit | | Happy Horse Retrieve Task / Retrieve Tasks | Query one or many existing task IDs | | Happy Horse Load Video | Decode a completed Ace media URL into native VIDEO |

All seven model IDs and all four generation actions in HappyHorseDify are offered, with model choices kept within their supported action. Model availability and pricing may differ by version and resolution.

Current version and install source

This source version is 0.1.2. Check GitHub Releases for its versioned ZIP. The Registry section below retains the last verified Active 0.1.0 on 2026-10-19; that older ZIP does not contain this release's updated guide, examples or fixes. To use this version, install its GitHub Release ZIP, or select the exact 0.1.2 Registry release once it becomes Active. Do not substitute the initial nightly selection for a verified stable release.

To install the GitHub ZIP, stop ComfyUI and back up any existing node directory. Extract the ZIP contents into ComfyUI/custom_nodes/happy-horse/ without adding an extra nested directory, run python -m pip install -r requirements.txt there, then restart and refresh. Keep the API Token in the actual launch-process environment. A GitHub ZIP install is separate from a verified Registry/Manager stable installation.

Install

Open the official Happy Horse by Ace Data Cloud Registry page, or open Manager → Custom Nodes Manager and search Happy Horse. The service is also known as HappyHorse; that no-space alias is being added to this package metadata, while the current public search is verified with Happy Horse. Use Ace Data Cloud as a fallback to find this publisher’s packages. Select Happy Horse by Ace Data Cloud, confirm publisher acedatacloud and source repository AceDataCloud/HappyHorseComfyUI, then click Install. In Select Version, explicitly select the approved Registry stable release 0.1.0. The normal dialog may initially highlight nightly; do not accept it for this stable-release tutorial. Keep dependency installation enabled. After Restart Required, restart ComfyUI and refresh the browser. Registry ID: happy-horse.

Actual ComfyUI-Manager list with this Ace service package

Actual Manager list after installation and restart

These are real 2026-10-16, ComfyUI 0.41.0 Linux screenshots from the publisher-brand installation test, not a new paid request or a screenshot of service-only search. See image sources and limits.

This Registry stable installation was verified on 2026-10-16 with original ComfyUI 0.41.0 on Linux CPU. That test did not submit a generation or chat request. Newer host versions and each paid action require their own checks; model availability and price remain subject to the current service rules.

For optional local source testing:

cd /path/to/ComfyUI/custom_nodes
git clone https://github.com/AceDataCloud/HappyHorseComfyUI.git
cd HappyHorseComfyUI
python -m pip install -r requirements.txt

This package targets ComfyUI 0.39.0 or newer because Load Video uses its native VIDEO type. Restart and search for Happy Horse.

Set your Ace Data Cloud key

Copy or create your own API Token

The Applications screen is shared across Ace integrations. 1 copies the existing token; 2 opens Manage Keys, then Create. A new account signs in/registers and initializes General application first. Verify this service's access, current price, balance and any expiry/Allowed APIs restrictions.

Ace Applications: copy token or open Manage Keys

Ace Create Key dialog

These masked 2026-10-08 Ace Console screenshots are reused from SunoDify. The example credential name in the second image is Dify tutorial; name yours ComfyUI. No credential was created by this guide update. Paste only the token into the environment of the process that launches ComfyUI (ACEDATACLOUD_API_KEY), then restart. There is no ComfyUI API Key textbox in these nodes; do not paste it into prompt/JSON widgets or the workflow file. An unrelated terminal export does not configure an already-running Desktop process.

  1. Sign in to Ace Data Cloud → Applications. If your account has no General application, choose Initialize General Application.
  2. Open General application and check access to the service used by this package. A service-specific application key is limited to that service. Copy an existing API key, or choose Manage Keys → Create for a separate key named ComfyUI.
  3. Copy only the token string, without Bearer or quotation marks. A platform management token is not the API key these nodes use. If you enable Allowed APIs, include every submission and task-query path used by your workflow. Check current pricing and available Credits before a paid action.

Use an application key with Happy Horse access. Set it in the ComfyUI process environment and restart:

export ACEDATACLOUD_API_KEY='paste-your-key-here'
python main.py --cpu

ACEDATACLOUD_API_TOKEN is also accepted. Keep the key out of workflows, screenshots, issues, and the repository. If you restrict API paths, allow /happyhorse/videos and /happyhorse/tasks.

Generate and retrieve

Import 01-submit-text-to-video.json with File → Open, select the model and price, then run once. Copy the task ID displayed by Preview as Text. A submitted task is not a completed video. If submission times out without an ID, inspect Ace request history before paying for another submission.

For I2V, enter one public HTTPS first-frame URL. For R2V, enter a JSON array or one URL per line with 1–9 references. For video edit, enter a public HTTPS video URL and optionally 0–5 reference images; origin preserves source audio. Each action only offers its compatible model IDs. T2V and R2V use the selected ratio; I2V follows the first-frame image ratio. Video edit duration follows the input video.

Import 02-retrieve-and-save.json, replace its placeholder task ID, then run. It connects Retrieve Task → Load Video → Save Video. Retrieve waits up to 240 seconds for the same task. If it remains pending, rerun only this retrieval workflow. The VIDEO output also connects to other native ComfyUI video nodes.

The read-only Retrieve Tasks node accepts a JSON array of 1–20 IDs and returns a compact JSON status list. It never submits a new video.

Check usage and troubleshoot

Check the submission by task or trace ID in the Ace Data Cloud Console. Read-only queries and media downloads should not create another generation.

| Symptom | Action | | --- | --- | | Key missing or HTTP 401/403 | Check the key in the running ComfyUI process and Happy Horse access. | | HTTP 429 | Wait for the service limit; keep any accepted task ID. | | Pending | Query the same task ID again; do not rerun a paid submit node. | | Submission timeout or HTTP 5xx | Inspect request history before resubmitting. | | Video download error | Confirm terminal success and an Ace CDN URL. |

Prompts and reference media URLs are sent to api.acedata.cloud; completed videos are downloaded from Ace CDN. See privacy notes. Only submit content you have permission to process.

Development

python -m unittest discover -s tests -v
python -m py_compile __init__.py client.py nodes.py

pyproject.toml declares short Registry ID happy-horse, publisher acedatacloud, and a 400×400 proportional resize of the canonical Ace logo.

Task lookup nodes refresh the same task on every queued execution rather than reusing a cached pending result. Paid submissions retain stable caching when inputs are unchanged, so refreshing a query does not resubmit generation. Disable auto-queue/auto-run before importing or running these workflows, and explicitly submit once.