n8n-nodes-pictify

This is an n8n community node. It lets you use Pictify in your n8n workflows to generate images, animated GIFs, and PDFs from HTML templates.

Pictify is the open API for rendering on-brand visuals at scale — Open Graph cards, social images, product photos, animated GIFs, certificates, invoices, and more.

Installation · Credentials · Operations · Example workflows · Resources

Installation

Follow the installation guide in the n8n community nodes documentation. In short:

1. Go to Settings → Community Nodes in your n8n instance.
2. Click Install.
3. Enter n8n-nodes-pictify and confirm.

After install, the Pictify node appears in the node picker.

Credentials

You need a Pictify API key. Create one at pictify.io → Settings → API Keys.

In n8n: Credentials → New → Pictify API

The credential is validated by calling GET /templates on save.

Operations

Image

• Render From Template — render a saved template with variables (e.g. OG cards, social posts). Supports layout/layouts variants and quality (0.1–1.0).
• Render From HTML — render raw HTML into an image. Style it with inline CSS or a <style> block (the image endpoint takes HTML only). Supports selector to crop to an element.
• Render Batch — submit an async batch render of one template across many variable sets (max 100). Returns a batch ID immediately; rendered URLs are delivered via the render.completed webhook (not in the node output).

GIF

• Render GIF — render an animated GIF from a template (+ variables) or from HTML. The source must animate (CSS animation / motion); a static source cannot be rendered as a GIF. Quality is a low / medium / high preset.

PDF

• Render PDF — render a PDF from a saved template by passing variables (uses the template render endpoint with format: pdf).

Template

• Get — fetch one template (returns the variables it accepts)
• List — list all templates on your account

Every operation supports the standard n8n options:

• Return Binary — download the rendered file and attach it as a binary property (great for emailing, uploading to S3/Drive, etc.)
• Continue On Fail — keep the workflow running even if one render fails

Example workflows

1. Generate an Open Graph image per blog post

Postgres → Pictify (Render From Template) — pull rows from your CMS, render an OG image per post using a saved Pictify template, save the URL back.

2. Email a personalised certificate as PDF

Webhook → Pictify (Render PDF, Return Binary) → Gmail/Send Email — take a name/course from a form submission, render a certificate PDF from a template, attach to email.

3. Animated product GIF for Slack alerts

Shopify Trigger → Pictify (Render GIF) → Slack — when an order ships, render a celebratory GIF and post it to a channel.

4. Bulk social-card generation

Google Sheets → Pictify (Render Batch) — submit up to 100 social-card variants from one template in a single async job (URLs arrive via webhook).

Resources

• Pictify API documentation
• Pictify templates gallery
• n8n community nodes documentation

Version history

1.0.0

• Re-pointed every operation to the live Pictify API (/image, /templates/:uid/render, /templates/:uid/batch-render, /gif, /templates).
• Image rendering from template (with layout/layouts, quality 0.1–1.0) and from HTML (selector, inline CSS).
• Async batch rendering (max 100 variable sets) — returns a batch ID; URLs arrive via webhook.
• Animated GIF rendering from template or HTML with low/medium/high quality.
• PDF rendering from a template (format: pdf).
• Template list / get.
• Binary download support.

License

MIT