How to Add a Chart to a Zapier Zap or Make Scenario
Want to see the output first? Render a chart in the playground. No account needed.
Zapier and Make are good at moving a row from one app to another. Neither draws a chart. If the weekly numbers land in a Google Sheet and the team reads Slack, you need a step in the middle that turns numbers into an image.
Both tools can do it with a Chart-Output API key. Zapier has an app with fields to fill in. Make uses its HTTP module. This guide covers both, and says plainly where each one gets awkward.
Before you build anything, paste this into a browser to see the kind of image you will get. No key and no sign-up:
https://www.chart-output.com/api/v1/render?type=bar&labels=Q1,Q2,Q3,Q4&data=42,58,51,73&width=800&height=400Anonymous requests are PNG only, capped at 1,200 pixels, and rate-limited per IP, so use them for previews. The steps below use an API key from the API Keys page. The Free plan needs no credit card and includes 1,000 renders a month. Free renders carry a small chart-output.com footer mark. See pricing.
Zapier
Render Chart
- Add an action to your Zap, search for Chart-Output, and choose Render Chart.
- Connect your account by pasting your API key. The connection check does not use up renders.
- Fill in the fields:
| Field | What to enter |
|---|---|
| Chart Type | Line, Bar, Pie, Doughnut, Radar, or Polar Area |
| Labels | Comma-separated, for example Mon,Tue,Wed,Thu,Fri |
| Data Values | Comma-separated numbers, for example 120,135,98,160,142 |
| Dataset Label | The name of the series |
| Width and Height | Pixels. Keep both at 1,200 or less on Free |
| Format | PNG, JPEG, SVG, or WebP on Free |
The action returns Chart Image URL, which you can use in any later step.
Example: a row of numbers to a Slack message
Say each new row in a Google Sheet has columns Mon to Fri. Trigger on New Spreadsheet Row, add Render Chart, and map the sheet columns into the fields:
- Labels:
Mon,Tue,Wed,Thu,Fri - Data Values: the five mapped column values, separated by commas
Then add a Slack Send Channel Message step and put Chart Image URL in the message text. For Gmail, set the body to HTML and use <img src="..."> with the same URL.
Render Template
Render Template fills a built-in template, such as MRR Trend, Signups by Month, or Plan Distribution, with your labels and values. It also takes a palette and a Brand Kit, either a saved kit's ID or one of the presets (obsidian, linen, polar, studio, ember, harbor). If you send charts for several clients, this is the action to use. The Template field lists the ones available.
Where Zapier gets awkward
- A Zap runs on one row at a time. A chart across many rows needs the values collected before the Render step.
- Render Chart draws a single series. For two series or a stacked bar, use a custom request to the API (see Make below, the body is the same) or switch tools.
Make
Make has no Chart-Output module, so use the built-in HTTP module and call the API directly. That gives you the full chart config, including multiple series.
- Add HTTP → Make a request.
- URL:
https://www.chart-output.com/api/v1/render - Method:
POST - Headers:
Authorization: Bearer YOUR_API_KEYandContent-Type: application/json - Body type: Raw, content type JSON.
- Request content:
{
"type": "bar",
"width": 800,
"height": 400,
"format": "png",
"returnUrl": true,
"data": {
"labels": ["Q1", "Q2", "Q3", "Q4"],
"datasets": [
{ "label": "This year", "data": [42, 58, 51, 73] },
{ "label": "Last year", "data": [38, 44, 47, 52] }
]
},
"options": { "plugins": { "legend": { "display": true } } }
}The options line turns on the legend. Without it a two-series chart renders with no legend, and nobody can tell which bars are which.
With "returnUrl": true and Parse response turned on, the module outputs a url field you can map into a Slack, Gmail, or Notion module. Without returnUrl, the response is the image itself as a file, which you pass to an Upload a file module instead.
To chart values from many rows, collect them first with an aggregator module, then map the aggregated values into the labels and data arrays. Module names and menus change between Make versions, so treat the steps above as the shape of the scenario rather than exact clicks.
Which one to use
| You want | Use |
|---|---|
| No code, one series, one row per run | Zapier, Render Chart |
| Client-branded charts without building JSON | Zapier, Render Template with a Brand Kit |
| Several series, stacked bars, or many rows | Make HTTP module, or an n8n workflow |
Limits worth knowing
- Every render counts toward your monthly allowance: 1,000 on Free, 25,000 on Pro.
- A chart that runs once a week is a few renders a month. A Zap that fires on every new row is not, so size the plan to the trigger.
- On Free, PDF output and sizes above 1,200 pixels are not available. If a request returns 403, that is usually why.
Every field the render endpoint accepts is listed in the OpenAPI spec, and charts in Slack, Discord, and Teams covers how each chat app handles image URLs.