Templated
Developer ToolsGenerate images, PDFs, videos, and HTML files from Templated designs by replacing text, image, color, and shape layers. Agents produce on-brand assets per record without a design request.
What This Integration Enables
Templated renders images, PDFs, videos, and HTML from a design your team built, replacing text, image, color, and shape layers with values from a record. That format range is unusual and it changes what the connector is for. A single approved design can produce the social graphic, the print-ready flattened or CMYK PDF, and a short MP4 with its own timing, which means the launch asset set stops being three separate production tracks that drift out of sync. Multi-page templates take this further: pass one set of layers to apply everywhere, or a per-page payload so each page of a deck or carousel carries different content, then merge the pages into one PDF or bundle them as a ZIP.
The second thing Templated does that its neighbors do not is treat each render as an object you continue to own. Renders are listed, retrieved by ID, duplicated, audited per template, and deleted. That inventory is what makes the connector viable for assets with a life after the send: a certificate someone asks to have reissued two years later, an invoice PDF that has to be produced identically on request, a video embedded on a page that outlives the campaign that created it. It also creates the obligation. A CDN URL that a live page depends on is a dependency, and the connector gives agents the operations to see that dependency before acting on it, which is where the human-in-the-loop gate on this service belongs.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Refreshing a product's asset set when the product changes
A price or packshot changes in Shopify. The agent calls List Template Renders to pull every asset previously generated from the product template for that SKU, then checks which of those URLs are still referenced by a live page or a scheduled campaign. It renders the replacements from the same design, saves each into FlowRunner file storage so a durable copy exists independently of the CDN, and posts the old and new sets side by side. Nothing is deleted until a person has looked at the list, because the superseded renders are the ones currently serving on real pages.
One design, several deliverables
An account team ships a client one-pager every month. From a single Templated design the agent renders the web image, a print-ready PDF with the pages merged, and a short MP4 for the client's internal channel, then drops the set into Dropbox and posts the folder link to Slack. Before a run of any size the agent calls Get Account to read how many API credits are consumed against the quota, because video and multi-page work draws harder than a single image and a batch that runs out halfway leaves a client set half delivered.
Documents issued on demand, and reissued years later
Certificates, tickets, and coupons are generated per record and their render IDs are written back to the record that caused them. When someone asks for a replacement, List Template Renders finds every asset ever produced from that design and the agent retrieves the original rather than rebuilding an approximation of it. Where a render is large enough to run asynchronously, the agent takes the webhook callback, confirms the status reached COMPLETED with Get Render, and calls Save Render To File Storage. If the render reports FAILED on a document that a customer is waiting for, the agent does not retry silently past a second attempt. It escalates with the template, the payload, and the failure so a person can decide whether the layout or the data is at fault.
Human-in-Loop Highlight
Delete Render cannot be undone, and when it runs the CDN URL stops resolving. That is a small operation with an unusually wide blast radius, because renders from this connector get embedded in published pages, sent emails, and customer records that keep pointing at the vendor URL long after the workflow that created them finished. So a cleanup agent never deletes on its own reasoning. It assembles the list, checks each URL against the pages and campaigns it can see, and stops: "42 renders from the Q2 promo template are superseded. 5 of them are still referenced by live pages, listed below. I have saved a copy of all 42 to file storage. Approve deletion of the 37 unreferenced renders, or approve all 42 and I will swap the live references first?" The agent does the work of knowing what is safe. The person decides what disappears.
Agent Capabilities
13 actionsRendering
6- Create Render Renders an image, PDF, video, or HTML file from one of your Templated designs, replacing the template's layers with supplied values. Pass Layers to apply the same modifications everywhere, or Pages to give each page of a multi-page template its own content. Supports custom dimensions and scaling, transparent PNGs, print-ready flattened or CMYK PDFs, MP4 timing, merging pages into one PDF or bundling them into a ZIP, and asynchronous rendering with a webhook callback. This is the production step.
- Get Render Retrieves a single render by ID with its status, output URL, dimensions, and source template. Used to poll for completion after an asynchronous render, and to confirm a render reached COMPLETED before anything downstream depends on the file.
- List Renders Lists every render in your account, newest first, with each render's ID, output URL, status, format, dimensions, and source template. Used to audit past generations or to recover a render URL nobody kept.
- Duplicate Render Creates a copy of an existing render using the same template and payload, returning a new independent render that can be customized separately. Duplicating counts towards the API quota, so it is a deliberate branch rather than a free copy.
- Delete Render Permanently deletes a render from your account. Deletion cannot be undone and the CDN URL stops resolving, which makes this the operation an agent should never reach for without an approved list behind it.
- Save Render To File Storage Downloads a finished render from the Templated CDN and stores a copy in FlowRunner file storage, returning both the FlowRunner URL and the vendor URL. Used for asynchronous renders and for keeping a durable copy of any asset that must survive a change in the vendor's hosting.
Templates
6- List Templates Lists the templates in your account with pagination, returning each template's ID, name, description, dimensions, thumbnail, and owner. Results can be narrowed by name, exact dimensions, tags, or your own external ID. Used to resolve which approved design applies to the record being processed.
- Get Template Retrieves a single template by ID with its name, description, canvas dimensions, background, thumbnail, layer count, and owner. Include Layers or Include Pages to also receive the definitions needed to build a render payload.
- List Template Layers Lists the modifiable layers of a template with each layer's name, type, editor description, and group. These layer names are the exact keys used in the Layers object of a render, so this is where an agent verifies that the payload it is about to send still matches the design.
- List Template Pages Lists the pages of a multi-page template together with the layers in each page. The returned page identifiers and layer names are what a per-page render payload is built from.
- List Template Renders Lists the renders previously generated from a specific template, with pagination and optional filtering by your own external identifier. Used to retrieve every asset produced from one design, such as every certificate ever issued from a certificate template.
- List Gallery Templates Lists the professionally designed templates in the public Templated gallery, filterable by name, description, category, tags, and dimensions. Gallery templates are read-only; opening or cloning one creates an editable copy in your account.
Account
1- Get Account Retrieves your account details including the plan, credits consumed, total quota, and percentage used. Used as a pre-flight check before a bulk render job so a batch does not stop halfway through a customer-facing set.
Frequently Asked Questions
What can FlowRunner do with Templated?
FlowRunner agents can run Create Render, Get Render, and List Renders in Templated, plus 10 more actions.
Does connecting Templated to FlowRunner require OAuth?
No. Templated connects to FlowRunner with an API key, no OAuth flow required.
Can Templated trigger a FlowRunner workflow automatically?
Templated doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Templated
$100 in credits. No card required. Connect in minutes.