Stencil

Stencil is an image and PDF generation API: design a template in its editor, then render it with your own text, images, QR codes, and barcodes. Agents create images and PDFs on demand, run collection batches, search past renders, and open editor sessions.

Verified 21 actions API key available

Stencil website Platform Documentation Capability data verified 2026-08-28

A copy or branding change is requested against a template that live flows render from

Get Template returns available_modifications, naming every field the design accepts

Search Images counts the assets already rendered from that template

Copy Template duplicates the design so live renders keep using the original

The agent posts the field list, the render count, and the layer permissions it proposes

The template owner approves the scope before Create Editor Session hands out an editing link

What This Integration Enables

Stencil is for teams whose asset volume has outgrown their design capacity but whose brand cannot afford to outgrow their design standards. A template is built once in Stencil's editor, and it publishes a contract: available_modifications names every editable field, its type, and whether it is required. Everything an agent is allowed to change is on that list, and everything else stays exactly as the designer left it. That split is the reason this connector belongs in an automation stack rather than in a creative tool. It lets a FlowRunner agent produce a thousand assets without ever being handed the ability to redesign one.

FlowRunner agents read the template contract, render images synchronously or as background jobs, produce PDFs from the same fields, fan one set of values across a whole collection, and search past renders by the values that went into them. That last capability matters more than it sounds: a flow can find the certificate it issued to a customer last quarter without having stored an id anywhere. Where this needs care is the one place Stencil is deliberately forgiving. A modification name the template does not have is ignored rather than rejected, so a mistyped field produces a perfectly successful render with that slot left at its default. This is exactly the class of automation exceptions FlowRunner is built to surface: the run that reports success while quietly being wrong.

Without FlowRunner

Design is the bottleneck Every per-customer certificate, badge, or campaign variant waits on someone opening a design file

Copy changes ripple by hand A price change or a new disclaimer means reopening every asset that carries it

Yesterday's asset is unfindable Rendered files scatter across drives under names that do not match the record they came from

With FlowRunner

Design is a contract, not a queue The designer owns the template, and the agent fills only the fields that template declares

One set of values, every surface A collection render turns one piece of content into every size the campaign needs in a single call

Assets are searchable by their content Renders are found again by the customer name or order number that went into them

Use Case Scenarios

Every enrollment ends with a document that already exists

A training completion is written to Airtable or a row lands in Google Sheets. The agent calls Get Template to read the certificate design's field list, builds the modifications array against that list rather than against a hard-coded map, and calls Create PDF And Wait so the finished file is available to the next step. The certificate is emailed through SendGrid and the URL is written back to the source record. If the same learner requests a reissue six months later, Search PDFs finds the original by their name instead of regenerating it and burning credits twice.
One announcement, rendered for every place it has to appear

A product update is approved in Notion. The agent takes the headline, the subhead, and the hero image URL, and calls Create Collection Images once. Stencil applies that single set of values across every template in the collection, so the post format, the story format, and the site banner all come back from one call with identical copy. Get Collection polls until the whole set reads done, because a partly rendered collection legitimately shows some empty URLs. The finished banner is pushed to a Webflow collection item and the social crops are posted to Slack for the channel owners to schedule. Nothing was resized by hand and no version of the copy drifted between formats.
A client edits their own template without ever getting an account

An agency runs one master template per client. When a client asks for a seasonal variant, the agent calls Copy Template to branch the design, then prepares a Create Editor Session request scoped to the layers the client is allowed to touch. The session link works without a Stencil login, which is the point, and it is also the risk. The agent posts the proposed permission set and the expiry to the account manager, who approves before the link is issued. Once the client has finished, Get Editor Session confirms the session has lapsed and the agency's rendering flows switch to the new template id.

Human-in-Loop Highlight

Create Editor Session issues a URL that lets anyone holding it edit a live template in Stencil's editor with no Stencil login at all, and this connector has no operation that revokes one. Get Editor Session can tell you a link exists and when it expires; nothing shortens that window. Naming a layer under the session's fields parameter also replaces the default actions for that layer rather than adding to them, so a permission set assembled from an incomplete list can hand out more access than anyone intended, against a design every future render depends on. So the agent prepares the session and stops. It posts: "Client request is a seasonal variant of Template 4412. That template has produced 2,140 renders across four active flows. The proposed session unlocks the headline and hero layers for 48 hours, and leaves the logo and legal footer locked. Issue it, or scope it differently?" The account manager answers. The agent does the copying, the field mapping, and the expiry tracking at machine speed. Handing out a key to the brand stays with a person.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

21 actions

Account and Projects

Get Account Reads the account behind the API key, its usage against the plan limit, and the renewal date. A Stencil key is scoped to one project, and this is the operation that names which one, so it doubles as the connection test.
List Projects Lists the projects the key can reach. Because keys are project scoped, a short list here describes the credential rather than an empty account.
Get Project Reads one project and confirms its id before a flow lists templates against it.

Templates

List Templates Lists a project's templates, each with the available_modifications array that names its editable fields.
Get Template Reads one template with the full set of fields it accepts and their types. This is the operation to call before writing a modifications array, because it is what the array has to match.
Copy Template Duplicates a design, optionally renamed and into another project. Used to branch a template per client or per campaign without rebuilding it in the editor.

Images

Create Image Renders a template and returns the finished PNG and JPEG URLs in the same response. The right choice for a single image inside a flow.
Create Image Async Queues a render and returns immediately with a pending record and empty URLs. Used for large batches and heavy templates where holding a connection open is unreliable.
Create Image Async And Wait Queues a render and polls until it is finished, returning the completed URLs. Used when the flow's next step needs the file but the template is too heavy for a synchronous call.
Get Image Reads a generated image by id. The outcome lives in the record's own status rather than the HTTP status, so this operation reports done and failed explicitly.
Search Images Finds previously generated images by the values that went into their modifications. This is how a flow retrieves its own earlier output by customer name or order number without having stored an id.

Collections

Create Collection Images Applies one set of modifications across every template in a collection, turning a single piece of content into a full set of formats in one call.
Get Collection Reads a collection render. Its status stays pending until every image in the set is finished, so a partly complete collection still shows empty URLs.

PDFs

Create PDF Renders a template to PDF from the same modifications used for images. Asynchronous only, and a PDF costs more against the plan than an image does.
Create PDF And Wait Queues a PDF render and polls until the file is ready. Used when the next step needs the document rather than a job id.
Get PDF Reads a generated PDF by id. As with images, the record's status is the real outcome and the file URL stays empty until it completes.
Search PDFs Finds previously generated PDFs by the values that went into their modifications. The document equivalent of Search Images, and the way a reissue avoids a second render.

Airtable

Run Airtable Action Starts a configured Airtable image generation run, so a flow can drive a whole base or view rather than one image at a time.
Get Airtable Action Status Reads the state of an Airtable action. Its status has no completed value, so an empty status following a started one is what finished looks like here.

Editor Sessions

Create Editor Session Creates a time limited link that lets someone edit one template without a Stencil login, with optional per layer permissions. The operation this page's human gate exists for.
Get Editor Session Reads a session, including the URL it hands out, the permissions it grants, and when it expires. Used to recover a link that was not stored, or to confirm one has lapsed.

Frequently Asked Questions

What can FlowRunner do with Stencil?

FlowRunner agents can run Get Account, List Projects, and Get Project in Stencil, plus 18 more actions.

Does connecting Stencil to FlowRunner require OAuth?

No. Stencil connects to FlowRunner with an API key, no OAuth flow required.

Can Stencil trigger a FlowRunner workflow automatically?

Stencil doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Stencil

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us