JsonCut

Put editable mediainside your n8n workflow.

Trigger image and video generation from forms, product data, CRM events or schedules without reducing the creative to a rigid node.

Let a workflow fill the design.Keep the design in Studio.

The JsonCut n8n workflow uses the JsonCut API to discover templates, upload media, submit renders and handle asynchronous results.

  • Inspect before mapping

    Load the template input contract so fields in the workflow match the actual creative project.

  • Handle media deliberately

    Use scoped uploads for files and pass stable project references to render steps.

  • Continue after rendering

    Poll or receive a webhook, then send the output to storage, publishing or review.

Made in JsonCut.Open one to see the project behind it.

Every title, clip and caption in these is still a layer. Open the project and change whatever you like.

Connect JsonCut.Render and deliver.

  1. Step 1

    Connect JsonCut

    Create an API key in Studio under Integrations → API keys and choose the project or template the workflow should fill.

  2. Step 2

    Map data and media

    See which fields the template has, upload your files and map only the values it needs.

  3. Step 3

    Render and deliver

    Start the render, wait for it to finish and pass the file to the next step.

What people make with it.

  • Catalog creative automation
  • CRM-triggered personalization
  • Scheduled social production

Before you start.The questions we hear most.

Do I need to build the visual in code?

No. Create and approve it in Studio, then expose typed fields for the integration.

Can the workflow generate images and video?

Yes. Both project types use the same media, template and job foundations.

How are large media files supplied?

Upload them as project media first and use the returned reference instead of embedding large base64 strings.

Design it once in Studio.Then hand it to n8n.