Tencent EdgeOne Image Render
Developer ToolsTencent EdgeOne Image Render turns an HTML and CSS template into a finished image at the edge. Workflows list templates, render images with dynamic data, and build signed image URLs safe to embed in email or dashboards.
What This Integration Enables
Most image generation tooling hands back a file, and a file has to be stored, served, and eventually cleaned up. Tencent EdgeOne Image Render hands back a URL. An HTML and CSS template lives in the Image Renderer console, variables travel in the link's query string, and the image renders at the edge on first request and is cached there. Build Signed Image URL computes that link locally without calling the API at all, which means the expensive-sounding part of this product costs nothing per view. That is the whole argument: an Open Graph card, an email header, or a completion certificate becomes a link a flow can produce in bulk and hand to anyone.
Two honest caveats, because they change how you would use this. Tencent labels the Image Renderer a beta and advises weighing the risk before production use, and PNG is the only output format supported today. FlowRunner agents work inside those limits rather than around them: they read a template's declared variables before rendering, check its audit status before publishing a link, and use Render Image when a flow genuinely needs the bytes to attach or upload. Where a generated link carries information about a specific person, FlowRunner's human-in-the-loop discipline is what keeps that decision with someone who can weigh it.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
Every published post gets its own social card
An article goes live in Contentful and the agent picks up its title, author, and section. Get Template parses the template's TemplateVariables so the agent knows exactly which keys the template accepts, which matters because EdgeOne rejects any key a template does not declare rather than ignoring it. Build Signed Image URL then computes the card link locally, and the agent writes it into the page's Open Graph metadata in Webflow and into the scheduled post. No file is stored anywhere, the first reader who shares the link triggers the render, and every reader after that is served from the edge cache.
-
Email headers that match the campaign, not the last one
A campaign is built in Mailchimp with a header image that changes per segment: different headline, different color, same layout. The agent builds one signed URL per segment against the same template, checks each template's AuditStatus first so a card that failed Tencent's content review does not ship as a broken image, and passes the links into the campaign content. When the design changes, the template changes in the console and every future link picks it up, because the link names a template rather than a rendered file.
-
Certificates issued at the moment they are earned
Someone finishes a course or passes an assessment, and the completion record reaches the flow. Render Image produces the certificate as PNG bytes, which is the right operation here because the file has to be attached to an email through SendGrid rather than linked. The agent checks the PNG came back as an image before storing it, since the render route answers with raw bytes and an error page would otherwise be filed as a broken certificate. The recipient's name is in the render request, and it stays there rather than traveling in a shareable URL.
Human-in-Loop Highlight
A signed EdgeOne image URL carries its variables in the query string, in plain view of whoever receives the link, and the edge caches the rendered result so that anyone who obtains the URL can load it. That combination is exactly what makes the product cheap, and it is also the thing that turns a personalized image into a disclosure. A header reading "Nice to see you again, Maria" is harmless. The same template rendered with an account balance, an internal deal stage, a customer identifier, or an email address is a record that has left the building, and the render is already sitting in a cache that FlowRunner cannot purge.
So the agent builds the template mapping and stops before the first batch of a new template ever leaves: "This template declares four variables. The campaign mapping fills them with first_name, plan_tier, renewal_date, and account_id. Every one of those will appear in the query string of a URL that goes to 4,100 recipients and renders for anyone who has the link. account_id and renewal_date are the two worth a second look. Send as mapped, drop them, or replace account_id with a non-identifying token?" A person decides what belongs in a public link. After that the mapping is approved and the run is unattended, because the question was about the template, not about each recipient.
Agent Capabilities
6 actionsConnection and templates
3- Verify Credentials Checks that the API Key and User ID are valid. Worth running once, because both values come from the Settings tab of a template in the Image Renderer console rather than from the main Tencent Cloud console, which is where people look first.
- List Templates Returns every image template in the account. Each row carries TemplateVariables, a JSON string naming the variables that template accepts, which is the contract a render has to satisfy.
- Get Template Returns one template's details, with TemplateVariables parsed into a variables object alongside the original string. Also reports AuditStatus, and a template marked abnormal has failed content review and will not render.
Producing an image
3- Build Signed Image URL Computes a signed EdgeOne image URL from the template and variables without calling the API at all. The best default here: the URL renders on demand at the edge and is cached there, so one build produces a link that serves an unlimited number of viewers.
- Get Signed Image URL Asks EdgeOne to produce the signed URL rather than computing it locally. It costs an API call where Build Signed Image URL costs none, so its real use is as a check that the local signature matches.
- Render Image Renders the template with your variables and stores the resulting image in FlowRunner file storage. The operation for when a flow needs the bytes rather than a link, to attach to an email or upload elsewhere.
Frequently Asked Questions
What can FlowRunner do with Tencent EdgeOne Image Render?
FlowRunner agents can run Verify Credentials, List Templates, and Get Template in Tencent EdgeOne Image Render, plus 3 more actions.
Does connecting Tencent EdgeOne Image Render to FlowRunner require OAuth?
No. Tencent EdgeOne Image Render connects to FlowRunner with an API key, no OAuth flow required.
Can Tencent EdgeOne Image Render trigger a FlowRunner workflow automatically?
Tencent EdgeOne Image Render doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other Developer Tools integrations
Start building with Tencent EdgeOne Image Render
Free plan, no card required. Connect in minutes.