npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@polotno/n8n-nodes-polotno-studio

v0.2.3

Published

Render images and videos from Polotno Studio templates

Downloads

530

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

lavrtonlavrtonnikigannikigan

Keywords

n8n-community-node-packagen8npolotnopolotno-studioimage-generationvideo-generationrender

Readme

@polotno/n8n-nodes-polotno-studio

This is an n8n community node. It lets you render images and videos from your Polotno Studio templates in your n8n workflows.

Polotno Studio is a content-automation platform that turns design templates into on-brand images and videos via a simple API. This package adds a node to fill a template's dynamic fields and render it, plus a trigger that fires when a render completes.

n8n is a fair-code licensed workflow automation platform.

Installation · Credentials · Operations · Trigger · Usage · Resources

Installation

Follow the community nodes installation guide and use the package name @polotno/n8n-nodes-polotno-studio.

Credentials

You need a project API key from Polotno Studio. To find it, sign in to Polotno Studio, open the editor, open the project selector, click Manage projects, and copy the API key for your project. Keys start with key_live_.

Create a Polotno Studio API credential and paste the key. n8n validates the key when you save the credential.

Operations

The Polotno Studio node has three resources:

Image → Render

Renders an image from a template.

  1. Pick a Template (search by name, paste a tpl_… ID, or paste a template URL).
  2. The template's Fields load automatically as typed inputs (text, image URL, color, toggle, …). Map values from earlier nodes or type them directly.
  3. Optionally set Format (PNG/JPEG/PDF), Transparent, and Pixel Ratio.
  4. Wait for Completion is on by default: the node waits for the render and outputs the final image_url. Turn it off to return the job immediately and continue via the trigger.

Video → Render

Renders a video (MP4/GIF) from a template. Same template + fields flow as images, plus FPS and Duration. Video renders are billed as ceil(duration) credits (1 per second; FPS does not affect cost) and can take longer — for long videos, turn Wait for Completion off and use the Polotno Studio Trigger instead.

Image / Video → Get

Fetches an existing render by its ID (img_… / vid_…) and returns its current state, including image_url / video_url once status is completed. Use this to retrieve a result from an async render (Render with Wait for Completion off, which returns only an id), to re-fetch what a webhook referenced, or to re-check a render that exceeded the wait window.

Template → Get / Get Many

List templates in your project (with optional Name, Tag, and archived filters) or fetch a single template by ID.

Trigger

The Polotno Studio Trigger starts a workflow when a render finishes. On activation it registers a webhook subscription with Polotno Studio; on deactivation it removes it. Choose which events to listen for:

  • image.completed / image.failed
  • video.completed / video.failed

The event's payload object (the completed image or video) is emitted as the workflow item.

Usage

A common pattern:

  1. A trigger (e.g. a new row in a sheet) starts the workflow.
  2. Polotno Studio → Image → Render: choose a template, map the row's columns onto the template fields, keep Wait for Completion on.
  3. Use the returned image_url in the next step (post to social, email, upload, …).

For high-volume or long video pipelines, render with Wait for Completion off and let the Polotno Studio Trigger continue the flow when each render completes.

Compatibility

Requires n8n 1.x. Tested against current n8n community-node tooling (@n8n/node-cli).

Resources

License

MIT