Easelly

Easelly turns a design built in its editor into a personalized infographic. Agents swap tagged text, colors, and images per recipient, then export the result as PNG, PDF, SVG, or JPG for reports, one-pagers, and campaign visuals.

Verified 7 actions API key available

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

A reporting cycle closes and per-client numbers are ready

Agent pulls each client's metrics and headline figures from the reporting source

Get Infographic Content lists the tags the template actually carries, and the agent maps its fields onto them

Duplicate Infographic applies one client's values to a copy, leaving the master canvas untouched

Get Download URL returns the finished PNG or PDF for that client

Account managers receive the links along with the tag map used to build them

The designer approves any edit to the master template itself before it takes the next run with it

What This Integration Enables

Easelly draws a line most design tooling leaves blurry. Objects on a canvas are edited through the API only if a designer tagged them in the Easelly editor, and untagged objects are not visible to the API at all. That is an allowlist for automation, decided by the person who owns the layout. The designer keeps typography, hierarchy, and composition. An agent gets a named set of text boxes, fill colors, and image slots that it is allowed to fill, and nothing else.

That boundary is what makes personalization at volume a reasonable thing to automate. FlowRunner agents read a canvas's tags, swap headline text, brand colors, and images per recipient, and export the result as PNG, PDF, SVG, or JPG. The work that used to be a designer's queue becomes a run, and the designer's time moves to the template. The judgment that stays with a person is which canvas a write lands on, because Easelly gives the connector both a non-destructive path and a destructive one, and the human-in-the-loop gate on this page sits exactly on that difference.

Without FlowRunner

Design is the bottleneck on volume Twenty personalized one-pagers means twenty trips through a designer's queue, so most months they do not happen

Copy and paste as a production method Someone duplicates last month's file and retypes the numbers, and the version that reaches the client is whichever one was open

The template is edited to make a variant A change meant for one client lands in the file everyone else's version is built from

With FlowRunner

Variants produced per recipient Each recipient's figures fill named slots in a design the team already approved

The numbers come from the source Values are read from the reporting system at build time, so the graphic and the dashboard agree

The master stays a master Personalization writes to copies, and the one operation that overwrites the original is a person's decision

Use Case Scenarios

A monthly client report that does not queue behind a designer

Month end closes, and per-client performance numbers land in Google Sheets. The agent calls Get Infographic Content once against the report template to read the tags it carries, then for each client calls Duplicate Infographic with that client's headline figure, sector color, and logo applied to the copy. Get Download URL returns a PDF link per client, and the links post to the account team in Slack with the tag map beside them, so anyone can see which value went into which slot. The master canvas is byte-identical at the end of the run to what it was at the start.
Campaign visuals built from CRM segments

A campaign needs a different lead visual per segment: different headline, different accent color, different hero image. The agent reads the segment definitions from HubSpot, builds one variant per segment through Duplicate Infographic, and exports each as PNG through Get Download URL. The image URLs go straight into the campaign in Mailchimp without anyone downloading a file. Because Get Download URL returns a hosted link rather than bytes, the run costs no file storage, which matters when a segmentation exercise produces forty variants instead of four.
The silent miss, caught before it ships

An entry whose tag does not exist on the canvas changes nothing, and Easelly does not report it. The export comes back looking untouched, which is indistinguishable from a design that simply did not need updating. So the agent never assumes its field names are right. Before a run it calls Get Infographic Content, compares the tags the canvas carries against the tags its mapping expects, and treats any unmatched name as an automation exception rather than an empty result. The first variant of any new template goes to a person with the tag list attached. After that the run proceeds unattended, because the contract has been checked against the canvas rather than assumed.

Human-in-Loop Highlight

Two operations here produce the same visual result and have completely different consequences. Duplicate Infographic copies the canvas, applies the changes to the copy, and returns an editor link, leaving the source design untouched. Update Infographic changes the canvas in place. For a run of variants, only one of those is correct, and the wrong one does not fail: it succeeds, the export looks right, and the template every future run is built from has quietly been replaced by one client's version of it. Easelly publishes no revision history in its API and no way to restore what the previous canvas held, so the correction is a designer rebuilding from memory.

The agent therefore uses Duplicate Infographic for every recipient, without exception, and never calls Update Infographic on its own initiative. When a change genuinely belongs in the master, such as a rebrand color or a new footer line, the agent prepares it and stops: "The Q3 report template's disclaimer tag still reads the 2025 wording. Applying the new text with Update Infographic overwrites the master canvas that all 34 client reports are built from, and there is no way to restore the current version through the API. Apply it, or duplicate to a new template first?" The designer answers. What kept the template safe was not the agent's care with the copy. It was that the write which cannot be undone belonged to the person who owns the design.

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

7 actions

Canvases and tags

List Canvases Lists the canvas ids on the account the key belongs to. Each id is a full URL rather than a short identifier, and it is that whole string every other operation expects.
Get Infographic Content Returns the tagged objects inside an infographic: each one's tag, type, text, fill color, and image source. The operation to run first for any canvas, because everything else here edits objects by tag, and a tag that does not exist changes nothing and is not reported.

Personalization

Duplicate Infographic Copies a canvas, applies the given object changes to the copy, and returns an editor link to it. The non-destructive way to personalize a template, and the operation a run of variants should use.
Update Infographic Changes an existing canvas in place: its tagged text, fill colors, and image sources. This overwrites the original, so a template edited by mistake takes every later run with it. The operation this page's human gate exists for.

Rendering

Get Download URL Applies changes to a canvas and returns a download link for the result in PNG, PDF, SVG, or JPG. The one to prefer: it covers all four formats, returns a link rather than bytes, and spends no flow file storage.
Generate PDF Renders an infographic to PDF with the given object changes applied. Easelly answers this route with the file itself rather than a link, so the result is stored in FlowRunner file storage and its URL returned.
Generate Image Renders an infographic to PNG with the given object changes applied. Like Generate PDF, this route answers with bytes rather than a link, so the file is stored and its URL returned.

Frequently Asked Questions

What can FlowRunner do with Easelly?

FlowRunner agents can run List Canvases, Get Infographic Content, and Get Download URL in Easelly, plus 4 more actions.

Does connecting Easelly to FlowRunner require OAuth?

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

Can Easelly trigger a FlowRunner workflow automatically?

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

Start building with Easelly

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us