Generate graphics from any Make.com scenario
Make scenarios can route almost anything. Point an HTTP module at your Drawtab pipeline and any step in the scenario can produce a finished, on-brand graphic.
What sets it off
Any Make.com scenario step you choose.
What you get
- Anything your template supports, from any Make-connected app
Setting it up
One-time setup. After this it runs on its own.
Create a Make pipeline
Pick Make.com in Drawtab Pipelines and choose your template.
Add an HTTP module
In your scenario, add HTTP → Make a request, set the method to POST and paste the pipeline’s trigger URL.
Send JSON fields
Set the body type to Raw with JSON content, and map your scenario’s values into it.
What you can put on the graphic
These are the paths you type into a template hotspot. Once a pipeline has received its first real record, the Sample Payload inspector shows your own data and you can click a value to fill the field.
| Field path | What it holds |
|---|---|
name | Recommended key for the recipient’s name |
email | Recommended key for delivery |
<any_key_you_send> | Every field in your JSON body is mappable |
How Drawtab knows the data is real
The pipeline’s secret trigger URL is the primary safeguard. Make can compute an HMAC if you want the extra layer — add the signature header in your HTTP module and set the matching secret in Drawtab.
Every pipeline also has its own secret trigger URL, which can be rotated at any time without touching your template or mappings.
Common questions
Can Make send the image on somewhere else afterwards?
Yes. Drawtab returns the rendered image URL in its response, so the next module in your scenario can post it to Slack, attach it to an email, or write it back to a record.
Other integrations
Start rendering from Make.com today
Set it up once, and every record from then on arrives as a finished graphic.