Orshot
Developer ToolsRender Orshot Studio designs or prebuilt library templates into PNG, JPEG, WebP, or AVIF images. Agents generate branded visuals per record without a design request.
What This Integration Enables
Most template renderers assume you already have a design. Orshot does not. It gives agents two paths to the same output, and the difference between them is the whole reason to pick this connector. Generate Image From Studio Template renders a design your team built in Orshot Studio, replacing its parameterized text, image, and color layers. Generate Image From Library Template renders one of Orshot's prebuilt utility templates instead: a website screenshot, a tweet image, an Open Graph image, a device mockup. The second path means a workflow can produce a competent share image on the day it is switched on, before anyone has opened a design tool.
Both paths come back as PNG, JPEG, WebP, or AVIF, with scaling and smart resizing to a channel preset or an explicit canvas, and multi-page templates cover carousels where each page needs its own content. Delivery is a choice: an Orshot-hosted link, or a decoded render saved into FlowRunner file storage when the asset needs to outlive the vendor URL. The discovery operations matter more here than on most rendering connectors, because Get Studio Template reports every modification key with its type and example value, which is what lets an agent build a valid payload against a design it has never seen. The tradeoff to manage is the one the library creates: convenience that fills a gap quietly is convenience that ships off-brand work without anyone deciding to.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Share image per post, driven by the design system
A post is published in Ghost or WordPress. The agent finds the Studio template tagged for that post type with List Studio Templates, reads its modification keys with Get Studio Template, and renders the share image with the post title, author, and category mapped onto those keys. It saves the render to FlowRunner file storage and writes the URL back to the post. The design was approved once. The variance lives entirely in the data.
A carousel from a single design
A multi-page Studio template covers a five-slide carousel. The agent supplies per-page content, renders the pages sized for the target network, and posts the set to LinkedIn with the caption assembled from the same source record. Because Orshot resizes to a preset or an explicit canvas in the render call, the same design serves several networks without a separate export pass for each.
Assets for a launch that has no design yet
A product launch needs a comparison page hero, screenshots of the feature in a browser frame, and a share image, and the design team is three weeks out. The agent renders these from Orshot's library templates instead, capturing the live pages with the website screenshot template and building the share image from the Open Graph template. That output is genuinely useful, and it is also not the company's design. Before any of it becomes a published asset, the agent puts the renders in front of the person accountable for the brand, because a screenshot template captures whatever is on that page at that moment, including a promotion or a price that will read as a commitment later.
Human-in-Loop Highlight
The gate on Orshot is the fallback, and it exists because the library is good enough to hide a problem. When List Studio Templates returns no design tagged for a post type, an agent that simply renders open-graph-image-1 instead produces a clean image that no one on the brand team ever approved, and it ships attached to the post. Instead the agent renders the fallback, stores it, and stops: "No Studio template is tagged for release-notes. I rendered this from the library template open-graph-image-1. Approve it as the share image for this post, or hold the post and I will queue a Studio design request." The same gate covers the screenshot templates for a different reason: those render live third-party pages, so the person approving is confirming that the captured state is one the company is willing to attach its name to. The agent produces the option. A person decides whether a generic asset is acceptable this time.
Agent Capabilities
6 actionsImage Generation
2- Generate Image From Studio Template Renders an image from one of your Orshot Studio templates by replacing its parameterized text, image, and color layers with supplied values. Supports PNG, JPEG, WebP, and AVIF output, scaling, smart resizing to a preset or an explicit canvas, and multi-page carousel templates. Choose a hosted URL, or have the render decoded and saved to FlowRunner file storage. This is the production step for on-brand assets.
- Generate Image From Library Template Renders an image from one of Orshot's prebuilt library templates such as website-screenshot, tweet-image, open-graph-image-1, or beautify-screenshot. Used when the workflow needs a competent asset before a design exists, and when the output is a capture of something rather than a composition of your own.
Studio Templates
2- List Studio Templates Lists the Studio templates in your workspace with pagination, returning each template's ID, name, description, tags, canvas size, thumbnail, pages, and modifiable parameters. Filter by a case-insensitive name substring and by tags. Used to resolve which approved design belongs to the record being processed.
- Get Studio Template Retrieves a single Studio template with its full list of modifiable parameters. Each modification reports its key, type, element name, example value, and the page it belongs to, which is exactly what an agent needs to build a valid payload for a design it has not seen before.
Library Templates
2- List Library Templates Lists Orshot's prebuilt library templates, each with the slug used as its template ID, a title and description, categories, supported output formats and delivery types, and the modification parameters it accepts. Used to discover what the library can cover before deciding whether a design request is required.
- Get Library Template Fields Returns the modification parameters accepted by a single library template, including each parameter's key, data type, description, and example values, plus the formats and delivery types it supports. Used to build a valid payload before rendering from the library.
Frequently Asked Questions
What can FlowRunner do with Orshot?
FlowRunner agents can run Generate Image From Studio Template, Generate Image From Library Template, and List Studio Templates in Orshot, plus 3 more actions.
Does connecting Orshot to FlowRunner require OAuth?
No. Orshot connects to FlowRunner with an API key, no OAuth flow required.
Can Orshot trigger a FlowRunner workflow automatically?
Orshot doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Orshot
$100 in credits. No card required. Connect in minutes.