Live render
Served by /chart at 560×300. The free tier caps the canvas at 1000 px per side; a key raises it to 3000 px per side (9 MP).
Recipes
Every automation tool can send an email. Almost none of them can draw a chart. The bridge is a URL: your workflow builds a chart URL, fetches the PNG, and attaches it — no chart plugin, no screenshot step, no rendering service to install.
Edit the form below and the chart re-renders live against our public /chart endpoint (free tier, 1000 px canvas). When the chart looks right, copy the URL into Zapier, n8n, Make or your own cron job.
Served by /chart at 560×300. The free tier caps the canvas at 1000 px per side; a key raises it to 3000 px per side (9 MP).
https://urlchart.com/chart?cht=bvg&chs=560x300&chd=t:12,19,14,23&chtt=Weekly+signups&chxl=0:|Mon|Tue|Wed|Thu&chxt=x,y&chco=2f5fe0
<img src="https://urlchart.com/chart?cht=bvg&chs=560x300&chd=t:12,19,14,23&chtt=Weekly+signups&chxl=0:|Mon|Tue|Wed|Thu&chxt=x,y&chco=2f5fe0" width="560" height="300" alt="Weekly signups: Bar chart of 4 values (Mon 12, Tue 19, Wed 14, Thu 23).">
Four actions and a test run. The one non-obvious part is that the URL has to exist as a single string: an HTTP step returns bytes, not a reusable link, so build the URL in a Formatter step and reference that field in both the fetch and the email.
chd.https://urlchart.com/chart?cht=bvg&chs=600x300&chd=t:
12,19,14,23 (your mapped values field)
&chtt= (your title)
&chxt=x,y&chco=2f5fe0
Keep the & separators literal. If a mapped value can contain a space or an & (a title usually does), run it through Formatter → Text → URL Encode first — the result is a URL, not a form post. If your plan's Formatter does not offer the concatenate transform, type the same string into the Webhooks URL field instead and repeat it in the email body.200 with an image/png body. If you only need a hosted link in the email, this step is optional — the link is the same string.<img src="…the Formatter output…" width="600" height="300" alt="Weekly signups">. Gmail's Send Email action has Body Type → HTML; Email by Zapier has a body field that accepts HTML. The recipient's client fetches the image when the message opens, so the URL must be publicly reachable — which it is.Attachment or inline image? Zapier's email actions send MIME parts, so the chart is normally an inline <img> the recipient's client loads. If the recipient needs the file itself, use the n8n recipe below, which fetches the PNG as binary data and attaches it.
The download below is a real n8n workflow export, not a screenshot of one. Import it with Workflows → Import from File and it arrives with the full chain already wired:
/chart URL with the data from the previous node.responseFormat: file, so the response becomes binary data instead of JSON.chart.png; connect your SMTP credentials and change the from/to addresses.The file uses only built-in n8n nodes (scheduleTrigger, set, httpRequest, emailSend), so importing it does not require installing a community package. Swap the Send Email node for a Gmail node if you send through Google; keep the binary property name the same.
Because the HTTP Request step stores a file, the workflow also works for the “chart in a nightly PDF” variant: replace the email node with a PDF or HTML-to-PDF node and reference the same binary property.
Most PDF generators accept a remote image URL directly — WeasyPrint, wkhtmltopdf, Puppeteer's HTML input, ReportLab's ImageReader, Google Docs exports, and the PDF nodes in Zapier, n8n and Make. You do not need to download the PNG first; hand the generator the same chart URL you put in the email.
<img src="https://urlchart.com/chart?cht=bvg&chs=600x300&chd=t:12,19,14,23&chxt=x,y&chco=2f5fe0">
Two practical notes: pin the pixel size with chs (a PDF page does not reflow an image), and use the @2x habit from the how-to if the report is printed — request double the width and let the layout scale it down.