n8n Workflow Templates for AI Image and Video

TL;DR: Download 12 free n8n workflow templates for AI image and video generation from the LinkModel GitHub repository. The collection covers GPT Image 2, Nano Banana models, Seedance 2.0 and 2.5, MiniMax H3, and Sora 2. Each JSON template already connects task creation, status polling, success and failure routing, timeout handling, and result retrieval.

These templates are for developers and automation builders who want to call generation APIs from n8n without rebuilding the asynchronous lifecycle for every model. You still choose the prompt, model parameters, trigger, storage destination, and retry policy; the repository provides a working orchestration layer to start from.

What are these n8n workflow templates?

An n8n workflow template is an exportable JSON definition of connected nodes. Importing one creates the nodes, parameters, expressions, branches, and canvas layout without requiring you to reproduce each step manually.

The LinkModel n8n collection is narrower than a general template directory. It focuses on one job: generating images and videos through the LinkModel API while handling the parts that are easy to miss in an asynchronous workflow.

Each template starts with a manual trigger and an editable Example Input node. It then creates a generation task, records the task ID, waits, queries the task status, and routes the response based on the result.

Example Input
     ↓
Create Generation Task
     ↓
Wait → Query Task Status
           ├── success → Format Result → Preview or Download
           ├── failed  → Stop with Error
           └── pending → Check Deadline → Wait and Poll Again

This separation matters for video generation. A video request can remain pending after the initial HTTP response, so treating task submission as the finished result creates incomplete or fragile automations.

Which image generation templates are included?

The repository currently includes six image templates. The flexible template exposes the model ID in the input node; the other five pin a specific model and its expected fields.

Every image workflow splits the returned image list and downloads the generated files into n8n Binary data. After a successful execution, open Download Generated Images → Output → Binary → data to preview or download the result.

Start with the flexible text-to-image JSON when your automation needs model selection as an input. Use the GPT Image 2 template or a Nano Banana template when you want a smaller, model-specific workflow.

For model selection beyond n8n, compare the current options in the AI image generation API guide and check the live text-to-image catalog.

Which video generation templates are included?

The repository includes six video templates, covering flexible model selection, Seedance, MiniMax, and Sora workflows.

The Seedance, MiniMax, and flexible workflows expose prompt, duration, size, and resolution in Example Input. The Sora 2 image-to-video template also accepts a public first_frame_image URL.

Use the Seedance 2.5 workflow JSON for clips up to 30 seconds, or the MiniMax H3 workflow JSON for an H3-specific starting point. The Sora 2 image-to-video template uses LinkModel's OpenAI-compatible video endpoint and a separate Header Auth credential.

Model parameters are not interchangeable. A flexible workflow makes the model ID editable, but it does not make every request field valid for every model. Check the live video model catalog before changing duration, resolution, aspect ratio, or reference inputs.

How do you import a workflow JSON into n8n?

You need an n8n instance, a LinkModel account, and an API key. The same steps work in n8n Cloud and self-hosted n8n when the included core nodes are available.

1. Open the LinkModel n8n workflow repository.
2. Select a JSON file under workflows/, then download the raw file.
3. In n8n, create a workflow and select Import from File.
4. Open the imported Example Input node and edit the prompt and generation parameters.
5. Configure authentication in both the task-creation and task-query HTTP Request nodes.
6. Select Execute workflow and inspect the final result or error node.

n8n documents both URL-based and file-based workflow imports in its official export and import guide. Imported credentials are not included in exported workflow JSON, so credential configuration remains an explicit setup step.

For example, the GPT Image 2 template begins with input shaped like this:

{
  "prompt": "A clean editorial product photo of a brushed aluminum speaker",
  "size": "1024x1024",
  "quality": "medium"
}

Edit values in the Example Input node rather than scattering them across several HTTP nodes. That keeps the workflow easier to review, duplicate, and connect to a webhook, form, spreadsheet, or database later.

How should you configure the LinkModel API key?

Create a key from the LinkModel API key dashboard. For a quick private test, the templates show where the Bearer header belongs in the create and query nodes:

Header Name: Authorization
Header Value: Bearer YOUR_LINKMODEL_API_KEY

For any workflow that will be saved, shared, or run by a team, create an n8n HTTP Header Auth credential and select it in both HTTP Request nodes. This avoids storing the secret directly inside node parameters.

The two requests must use the same account context: one creates the task and the other queries its status. A missing or inconsistent credential commonly produces an authentication error before the workflow reaches its polling loop.

How does polling and timeout handling work?

The templates do not use one long-running HTTP request. They submit the generation job, save its task_id, and poll the query endpoint until the task succeeds, fails, or reaches the workflow deadline.

The included video workflows use a finite deadline instead of polling forever. For production use, adjust the deadline and wait interval to your queue expectations, then decide whether an n8n execution retry should query the existing task or create a new paid generation. Blindly submitting another task can duplicate both output and cost.

How do you turn a template into a production workflow?

The downloadable templates are intentionally small. They prove the generation lifecycle, but your trigger, persistence, observability, and business rules belong in your own workflow.

Use this implementation checklist before activating one in production:

1. Replace the manual trigger with a webhook, form, schedule, queue, or application event.
2. Move authentication into an n8n credential and restrict who can edit it.
3. Validate prompts, URLs, durations, aspect ratios, and model IDs before task submission.
4. Add an idempotency key or processed-state check around external triggers.
5. Save task_id, model, input, timestamps, and final status for debugging.
6. Copy successful media to durable storage such as S3, R2, Drive, or your asset pipeline.
7. Separate retrying a status query from creating a new billable task.
8. Add an error workflow or notification for failed and timed-out executions.

Generated media URLs can be signed and temporary. The included templates download many outputs into Binary data for convenient inspection, but execution storage is not automatically a permanent media library. n8n's binary data documentation explains the data type; your hosting and retention design determines where long-lived assets should go.

Which template should you start with?

Choose the smallest template that matches the first result you need:

• Start with GPT Image 2 when you want one prompt-to-image automation with explicit size and quality controls.
• Start with Nano Banana 2 when your roadmap already centers on Google's current image family.
• Start with Seedance 2.5 when longer narrative video and a standard polling lifecycle matter.
• Start with MiniMax H3 when H3 is already the selected video model; its model ID is case-sensitive.
• Start with Sora 2 image to video when a public first-frame URL is part of the input.
• Start with a flexible template when model switching is a workflow requirement rather than a one-time setup choice.

Avoid starting with a large social publishing automation if your generation request is not yet stable. First confirm authentication, parameters, polling, and file persistence; then connect Sheets, Drive, Slack, Telegram, or publishing nodes.

Frequently asked questions

Are the LinkModel n8n workflow templates free?
Yes. The workflow JSON files are free to download from the public GitHub repository. Running image or video generation requests consumes LinkModel API credits according to the selected model and settings.

Do the templates work with n8n Cloud and self-hosted n8n?
The templates use n8n core nodes such as Manual Trigger, Set, HTTP Request, Wait, If, Switch, and Stop and Error. They are designed to be importable in n8n Cloud or self-hosted n8n, but you should verify them against your installed n8n version and execution-storage configuration before production use.

Can I switch models inside the same n8n workflow?
Yes, the flexible image and video templates expose the model ID in the Example Input node. Request fields remain model-specific, so switching the ID may also require changing duration, resolution, size, quality, or reference inputs.

Why does an AI video workflow need polling?
Video generation is asynchronous: the create request returns a task before the final video is ready. The workflow must query that task until it succeeds, fails, or reaches a timeout instead of treating the initial response as the finished media.

Where should an n8n workflow save generated images and videos?
Use n8n Binary data for immediate preview or downstream processing, then copy important files to durable object storage or a media system. Do not rely on a temporary signed result URL as permanent storage.

Can I use one LinkModel API key for image and video workflows?
Yes. A LinkModel API key can authenticate requests across supported image and video models available to the account. Keep the key in an n8n credential and confirm each model's current availability in the LinkModel catalog.

The bottom line

A useful n8n template is not necessarily the one with the most nodes. Start with the smallest workflow that exposes the real task lifecycle, fails visibly, and leaves clear places for your trigger, credentials, storage, and business rules.

Download the 12 LinkModel workflow templates, create an API key, and run one model-specific workflow manually before adding the rest of your automation.

Sources: LinkModel n8n workflows, n8n workflow export and import, n8n HTTP Request node, and n8n Wait node. Keyword data: Ahrefs, United States, checked August 28, 2026.