Canvasflare
Developer ToolsTurn HTML and CSS into images through Canvasflare's headless Chrome rendering API, or capture a screenshot of a live URL. Agents produce social cards, receipts, and report visuals without running a browser.
What This Integration Enables
Canvasflare is built for teams that would rather keep their template in their own hands than in someone else's dashboard. There is no stored-template system here, and that is the point: the agent supplies the full markup on every call and interpolates flow data into it, so the design that produces your branded assets sits next to the logic that fills it and gets reviewed the same way. FlowRunner agents call Render Image with HTML and CSS and get a hosted image back synchronously, with no polling step and no callback to wait on, which keeps a rendering step from turning into a state machine.
The same headless Chrome engine also captures live pages. An agent can screenshot a public URL, inject CSS to hide a cookie banner before the shot, crop to a single element with a selector, and emulate a specific phone or tablet viewport chosen from List Emulation Devices. Rendered files can be copied into FlowRunner file storage with Save Image To Storage, which matters because Canvasflare-hosted images can be deleted or expire while an email that references them is still in someone's inbox. These are connectors in the sense FlowRunner means it: a bounded, reusable bridge that an agent calls when it needs pixels, and a place where the agent can stop and ask before it spends.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Share cards for a product catalog that changes daily
A commerce team adds products throughout the day in Shopify. Overnight, an agent collects the new records, renders an Open Graph card for each one by interpolating the title, price, and hero image into the template held in the flow, and calls Save Image To Storage so the asset survives independently of the Canvasflare copy. The card URL is written back to the product record so the storefront and the social preview agree. Before the run starts, the agent reads Get Plan Usage, so a 900-product day does not quietly become 400 cards and 500 blanks.
Visual monitoring of pricing and landing pages
A competitive intelligence workflow runs Capture Screenshot against a list of public pages on a schedule. Extra CSS suppresses cookie banners and consent overlays so consecutive captures are actually comparable, and a CSS selector crops each shot to the pricing table rather than the whole page. Captures land in Amazon S3 through file storage, and a summary with the images posts to a Slack channel. The team sees what changed instead of reading a diff of HTML.
Device-accurate previews before a campaign ships
Before an email campaign goes out through SendGrid, an agent renders the campaign's landing page across several emulated devices pulled from List Emulation Devices, assembles the results into a review post, and holds the send. Someone looks at the phone-width render, sees that the hero headline wraps badly on a small viewport, and fixes it before the campaign reaches a list rather than after.
Human-in-Loop Highlight
Canvasflare bills per render and caps concurrent requests, which makes a bulk run the one place an agent can do real damage on its own. Get Plan Usage reports exactly this: requests included in the period, requests used, requests remaining, and how many simultaneous calls are still available. So before a batch, the agent reads it and does the arithmetic. When a 4,000-row catalog run meets 1,200 remaining renders, the agent does not start and hope. It pulls the digital andon cord and posts to the marketing ops channel: "Catalog card run needs 4,000 renders. 1,200 remain in this period and the concurrency allowance is 3. Options: render the 1,200 highest-traffic SKUs now, upgrade the plan, or hold until the period resets on the 1st. Which?" The reason this gate has to exist is that a half-finished run is worse than no run at all. Spent renders are not refundable, and the 2,800 products that got nothing still go out to a list with a broken preview attached. A person picks which of those outcomes they are willing to own.
Agent Capabilities
7 actionsImage Rendering
2- Render Image Renders an image from raw HTML and optional CSS in headless Chrome and returns the hosted URL. Rendering is synchronous, so the flow continues the moment the image exists. Used whenever a flow needs a branded asset built from record data: a share card, a receipt, a certificate, a ticket, a report visual.
- Capture Screenshot Captures a publicly reachable webpage and returns the hosted URL of the resulting image. JavaScript-driven content renders normally because the page loads in a real browser, and extra CSS can be injected before capture to hide overlays. Used for archiving, competitive monitoring, and page previews.
Image Management
2- Get Image Looks up a previously rendered image by its id and returns the URL it is served from. Used to re-resolve an asset whose id was stored earlier, or to obtain a link that downloads rather than displays.
- Delete Image Permanently removes a rendered image from Canvasflare storage. Used to clean up short-lived previews and one-off cards so they stop being publicly reachable. The operation cannot be undone, so anything still pointing at that URL breaks.
Files
1- Save Image To Storage Downloads a rendered image and stores it in FlowRunner file storage, returning both the FlowRunner URL and the original. Used immediately after a render when the asset needs to outlive Canvasflare expiry, be attached to an email, or be uploaded somewhere else in the flow.
Configuration
1- List Emulation Devices Lists every device Canvasflare can emulate, with user agent and viewport metrics including width, height, scale factor, touch support, and orientation. Used to discover the identifier to pass as the emulated device, or to confirm a viewport before choosing it.
Account
1- Get Plan Usage Reports consumption for the current billing period: requests included, used, and remaining, plus the concurrency allowance and how much of it is free. Used as the preflight guard on any batch, so the flow escalates on quota rather than failing partway through.
Frequently Asked Questions
What can FlowRunner do with Canvasflare?
FlowRunner agents can run Render Image, Capture Screenshot, and Get Image in Canvasflare, plus 4 more actions.
Does connecting Canvasflare to FlowRunner require OAuth?
No. Canvasflare connects to FlowRunner with an API key, no OAuth flow required.
Can Canvasflare trigger a FlowRunner workflow automatically?
Canvasflare doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Canvasflare
$100 in credits. No card required. Connect in minutes.