HappyHorse by AceDataCloud — n8n community node

Create HappyHorse videos from text, first frames or reference images, edit existing videos, and track generation tasks in n8n via AceDataCloud.

Package: @acedatacloud/n8n-nodes-happyhorse · License: MIT · Node: HappyHorse by AceDataCloud

Maintained by Ace Data Cloud, connecting to AceDataCloud's API. This is not an official package from the model developer. A direct provider subscription does not supply an AceDataCloud API credential.

What you can build

• Turn campaign briefs into short videos.
• Animate a first frame or guide a scene with reference images.
• Edit existing clips and preserve original audio when requested.

Installation

In self-hosted n8n, open Settings → Community nodes → Install, enter @acedatacloud/n8n-nodes-happyhorse, review the package and install. To reproduce this release exactly, use @acedatacloud/[email protected].

See n8n's installation guide. n8n Cloud requires verified community nodes. npm publication and verification are separate; check the n8n node panel for current Cloud availability.

Operations

| Resource | Operation | Result | | --- | --- | --- | | Video | Generate | Text-to-video | | Video | Image to Video | Animate a first-frame image | | Video | Reference to Video | Generate from 1–9 reference images | | Video | Edit | Edit a source video with up to 5 optional references | | Task | Get | Retrieve one task's state, result, error and reported cost | | Task | Get Many | Retrieve up to 50 explicit task IDs as separate n8n items |

Credentials

1. Open Ace Data Cloud → Applications. Sign in, or register an account first.
2. Find General application. If it has not been created, choose Initialize General Application. A general key can use the services available to your account; a dedicated application's key is limited to its service. Check the required service/model access and current pricing.
3. Copy the API Key from the application card, or open Keys / Manage Keys → Create to create a separate key for this integration. Give it a recognizable name so you can revoke or rotate it independently.
4. When creating a key, review Expiration Time, Set Usage Limitation, and Allowed APIs. Enable only the restrictions you need, allow the operations you will call, then click Create and copy the token from the key list. Task lookup does not grant permission to submit a generation. Confirm the application's balance can cover your first request; any trial allowance is whatever your account currently displays.
5. Copy only the token value, without quotation marks, spaces, or Bearer . An API Key / API Token field expects this raw value; only a manually configured HTTP Authorization header needs the Bearer prefix. A platform-... account-management token cannot replace a generation API key.

Save the key in the client's credential store or the environment variable shown below. Never put it in a prompt, shared workflow, screenshot, or Git commit. If authentication fails, check the full copied value, application/service access, expiration, usage limit, and balance before creating another key.

In n8n, open a node and create a HappyHorse by AceDataCloud API credential. Paste the raw value into API Token, save, and select this credential on every node that needs it, including task readers.

The token is masked and stored in n8n's credential store. The node sends Bearer authentication only to https://api.acedata.cloud. Its credential test queries an empty task batch and does not generate media. Do not use a platform management token.

Quick start and examples

Import Generate and wait, assign credentials to Create and Get Task, and edit the generation parameters. One manual execution submits once, then queries every 15 seconds. The loop has a 30-minute deadline and explicit failure handling. A deadline stops waiting; it does not cancel a submitted service task.

Import AI Agent task tool to use the node as a read-only tool. Replace the sample task ID, configure the chat model and select the service credential. The agent queries a task once; it does not create media.

Additional examples are in examples/. They contain no credentials and no pinned or fabricated output.

Example output

Open a real video result generated through this node with happyhorse-1.1-t2v during live validation.

Parameters and limits

• Select the matching 1.0/1.1 model for each operation. Video Edit currently uses happyhorse-1.0-video-edit. The node validates the operation/model pair.
• Generation duration: 3–15 seconds. Resolution: 720P or 1080P.
• First-frame mode follows the source image ratio. Text and reference modes expose aspect ratio controls.
• Video Edit is billed on the combined input and output video duration. The final result reports the billable duration; it can differ from the output duration alone.

Output and task states

With Simplify enabled:

• Generation returns taskId, status: "submitted", finished: false, successful: null and traceId.
• Task queries return taskId, status (processing, succeeded or failed), finished, successful, data, error, traceId and cost.
• Final media URLs are inside data. Fish TTS responses with a top-level audio_url are exposed as data.audio_url.
• A submission acknowledgment is not a finished result. Continue only when finished is true and successful is true.

Disable Simplify to receive the API response unchanged. Batch queries emit one item per task, preserving the relationship to the originating n8n input item.

Billing, retries and errors

Generation uses your AceDataCloud balance. Check current API documentation and pricing before execution. cost.amount is in Credits, not USD; the conversion depends on your current package rate.

Each incoming n8n item sends one generation request. Creation is not retried automatically and the node does not substitute a different model. Re-running Create, enabling retry-on-fail, or restarting the workflow can create another paid task. After a timeout, retrieve the existing task where possible.

HTTP/authentication/parameter errors fail the node with the API's error context. Completed failed tasks are represented as finished: true, successful: false and an error, so downstream nodes can handle them. n8n's continue-on-fail option emits an error item and proceeds with later input items.

Data handling and compatibility

Only configured text, model choices, media references and query parameters are sent to AceDataCloud. Input URLs must be accessible to the API. The node has no filesystem access, environment-variable access or telemetry, and no runtime dependencies beyond n8n's workflow API.

Built with the official @n8n/node-cli, strict community-package rules and Node.js 24. CI loads the package in n8n 2.42.3. Older n8n versions are not part of this release's compatibility test matrix. Icons are bundled from the existing Studio/service catalog; see asset provenance.

Development

pnpm install --frozen-lockfile
pnpm run build
pnpm run lint
pnpm test

Programmatic nodes validate conditional media payloads, normalize asynchronous task responses and preserve input-item links. All service requests use n8n's authenticated HTTP helper. Unit tests mock the HTTP boundary; they do not incur generation charges.

Releases are built from merged source through GitHub Actions with npm publish --provenance. Publication runs build, lint and tests. Keep published versions immutable and update CHANGELOG.md for new releases.

Resources and support

• API documentation
• AceDataCloud Studio
• Report an issue
• n8n community-node documentation

Include the package version, n8n version, operation and a redacted error when reporting issues. Never include API tokens or private media.