Skip to content

How to Automate AI Video Generation With n8n and Make

2026-10-02 · blog how-to · Higgsfield · original

Topic: Higgsfield platform & ecosystem (also: Studio work & business, Cost, credits & plans, Post-production & finishing) · mode: Tutorial · tags: flattened table

A Higgsfield how-to from 2 October 2026 for agencies that want to automate video production by connecting Higgsfield to n8n or Make and delivering the results to clients. There are two routes: the API, paid per second from a prepaid dollar balance, for server-side production; or MCP, which spends an existing plan's credits. It gives step-by-step setup for both tools, notes that Veo 3.1 is missing from the API and that Unlimited does not apply outside the website, and says clients can own the videos while the API itself cannot be resold.

What is said

  • Questions answered: subscription, route, one key, Unlimited, nodes, file storage

What is said

★ — how much it matters to the source.

  • ★★★ Higgsfield's blog says an AI automation agency can connect Higgsfield to the orchestrators n8n and Make and deliver the finished videos to clients.
  • ★★ Higgsfield's blog says scale is usually an agency's hard part: different client briefs may need different models, and a separate vendor, API key and integration for each adds setup work before generation.
  • ★★★ One Higgsfield API key and one request lifecycle open 50+ video and image models, from Seedance and Kling to Higgsfield's own Cinema Studio 4.0 and Marketing Studio. · Higgsfield API, Seedance, Kling, Cinema Studio 4.0, Marketing Studio
  • ★★ For teams already on a Higgsfield plan, Higgsfield MCP connects n8n and Make to the same higgsfield.ai account used on the website, and the results land in Assets. · Higgsfield MCP
  • ★★ The Higgsfield API and Higgsfield MCP are two different products, each with its own account and billing; Higgsfield's blog says the right route depends on how the agency runs volume. · Higgsfield API, Higgsfield MCP
  • ★★★ Every Higgsfield API generation is paid from a prepaid US-dollar API balance, video is priced per second of output, failed generations are not billed, and the minimum top-up is $5. · Higgsfield API
  • ★★★ Through Higgsfield MCP generations deduct plan credits at standard rates, $1 being 20 credits; plans run Starter $15/mo, Plus $49/mo ($39 annual) and Ultra $129/mo ($99 annual). · Higgsfield MCP, credit, Starter plan, Plus plan, Ultra plan
  • ★★ n8n and Make both ship an MCP Client; in Higgsfield's test Higgsfield MCP connected to both with a regular account sign-in and no API key, and it requires an active paid subscription. · Higgsfield MCP
  • ★★ Soul ID characters are available through the Higgsfield API from $2.50 per request, and through Higgsfield MCP. · Soul ID, Higgsfield API, Higgsfield MCP
  • ★★ The Higgsfield API returns a file URL to the workflow, while Higgsfield MCP results land in Assets on higgsfield.ai plus a result URL. · Higgsfield API, Higgsfield MCP, Plus plan
  • ★★★ Higgsfield advises the Higgsfield API for pay-as-you-go production workflows that need server-side control and an API key, and Higgsfield MCP when n8n or Make should work through an existing Higgsfield account and its plan credits. · Higgsfield API, Higgsfield MCP
  • ★★★ Veo 3.1 is not in the Higgsfield API catalog; it is available on the website and through Higgsfield MCP, so workflows built on the API route cannot call it. · Veo 3.1, Higgsfield API, Higgsfield MCP
  • ★★ Every Higgsfield API generation is asynchronous in four stages; first the workflow sends a POST to the model's endpoint on api.higgsfield.ai and receives a request id, a status url and a cancel url. · Higgsfield API
  • ★★ A Higgsfield API request moves through queued and in progress to a final status: completed, failed, nsfw or canceled. · Higgsfield API
  • ★★ A webhook URL goes in the hf webhook query parameter of each Higgsfield API request, with delivery retries for up to 2 hours; polling the status url every 2 to 10 seconds is the fallback. · Higgsfield API
  • ★★ Higgsfield API output files stay available for at least 7 days, so Higgsfield advises the workflow to copy them to the agency's own storage. · Higgsfield API
  • ★★ Failed Higgsfield API generations are not billed, and the amount returns to the balance automatically. · Higgsfield API
  • ★★★ To call the Higgsfield API from n8n: create a Header Auth credential (header Authorization, value "Key KEY_ID:SECRET" with a key from open.higgsfield.ai), then an HTTP Request node posting to the model's endpoint with a JSON body of prompt and settings. · Higgsfield API
  • ★★★ In n8n a Wait node set to resume on a webhook call, with {{ $execution.resumeUrl }} in the hf webhook parameter, continues the run when the Higgsfield generation finishes; the output URL is read from the webhook payload. · Higgsfield API
  • ★★ When a public webhook address is not an option, Higgsfield advises a polling loop in n8n with an HTTP Request node against the Higgsfield API status url as a backup. · Higgsfield API
  • ★★★ In Make, one scenario sends the Higgsfield API request through the HTTP module with the Authorization header and puts a second scenario's Custom webhook address in hf webhook; the second scenario receives the result and handles delivery. · Higgsfield API
  • ★★ A single-scenario alternative in Make puts the Sleep module between the Higgsfield API request and a status check against the status url, repeated until the status is final. · Higgsfield API
  • ★★★ To connect Higgsfield MCP in n8n: add the MCP Client node with Server Transport HTTP Streamable, endpoint https://mcp.higgsfield.ai/mcp and Authentication MCP OAuth2, create the credential with Dynamic Client Registration on, then sign in to Higgsfield. · Higgsfield MCP
  • ★★ After sign-in Higgsfield MCP lists generation tools for images, video and audio, batch versions, upscales and Marketing Studio next to utility tools; parameters go into one JSON field, such as model, prompt and "get cost": true. · Higgsfield MCP, Marketing Studio, upscaling
  • ★★ In n8n a second MCP Client node runs the Higgsfield MCP jobs wait tool with the returned job id to receive the final status and the result URL. · Higgsfield MCP
  • ★★★ To connect Higgsfield MCP in Make: add the MCP Client app with the Call a tool action, connect a new MCP server with the same URL, leave the token empty and sign in through OAuth, then pick a tool and pass the arguments as one JSON field. · Higgsfield MCP
  • ★★ In Higgsfield's Make test, switching Higgsfield MCP tools did not always refresh the argument fields; recreating the module resolved it. · Higgsfield MCP
  • ★★ In Higgsfield's testing, the Higgsfield MCP get cost parameter returned a request's price without starting a job, and jobs wait consumed no generation credits. · Higgsfield MCP, credit
  • ★★ Make meters its own operations separately from Higgsfield credits, so the orchestrator's billing applies on top. · credit
  • ★★ n8n runs in the cloud or self-hosted while Make is cloud only; for an agency keeping API keys on its own infrastructure, Higgsfield calls self-hosting the main structural difference.
  • ★★★ Higgsfield advises n8n for self-hosting and more control over workflow infrastructure and Make for a fully cloud-based visual workflow; both run Higgsfield through the API or MCP. · Higgsfield API, Higgsfield MCP
  • ★★★ Higgsfield does not claim ownership of generated outputs or restrict their commercial use, and rights in exported outputs can be transferred or sublicensed to clients. · Higgsfield AI
  • ★★★ The Higgsfield API cannot be resold or exposed as a standalone generation service; its use is governed by the Higgsfield API Terms of Service together with the Terms of Use. · Higgsfield API
  • ★★ Higgsfield's terms restrict sharing the API key with anyone, clients included, and sharing the higgsfield.ai account or its login, while rights in exported outputs are kept after a subscription ends. · Higgsfield API
  • ★★ Higgsfield's blog says the agency keeps control of the Higgsfield account and credentials while the client receives the finished files, and commercial rights in outputs do not depend on the plan.
  • ★★ Higgsfield API prices vary by model and configuration, so Higgsfield advises using the cost estimate endpoint for the current price before running production jobs. · Higgsfield API
  • ★★★ Higgsfield API parallel capacity scales with funding over the last 28 days: up to $25 gives 2 concurrent requests, from $25 10, from $100 20, from $1,000 40; higher limits through sales. · Higgsfield API
  • ★★ Higgsfield says recurring generation on a schedule does not always need n8n or Make: Supercomputer runs scheduled, multi-step generation jobs on higgsfield.ai with plan credits and no external setup, only on the website. · Supercomputer, credit
  • ★★★ As of October 2026 there is no official first-party Higgsfield node for n8n or Make, while HeyGen and Creatomate list ready-made connectors in both. · HeyGen
  • ★★★ Higgsfield Unlimited access does not apply outside the website: API generations are paid from the API balance and Higgsfield MCP generations always deduct plan credits. · Higgsfield API, Higgsfield MCP, credit
  • ★★ The webhook URL must be included with each Higgsfield API submission, since the hf webhook parameter is set per request. · Higgsfield API
  • ★ One Higgsfield API key accesses the image and video models of the API catalog; each model has its own endpoint and request parameters under the same account and authentication. · Higgsfield API

Threads in this video

Mentioned

Central: Higgsfield API · Higgsfield MCP · Make · n8n

Also: Organizations: Creatomate · HeyGen

Concepts: AI automation agency · credit

Products: Cinema Studio 4.0 · Kling · Marketing Studio · Plus plan · Seedance · Soul ID · Starter plan · Supercomputer · Ultra plan · Veo 3.1

Replies to

Replied to by

← Previous: Did AI Change Editing Forever? (GPT-6 Astra + DaVinci Resolve) · Next → Realistic Characters From Simple Sketches #AI #Animation #Design