How do I integrate an image automation API with Make.com?

Make has a native module for this, so you do not need to build a raw HTTP call. You add the module to a scenario, connect it with your API key, choose your template, and map data from your trigger into the template layers. When the scenario runs, it renders the image and returns the result.

Setting up the scenario

A basic scenario has a trigger and the render action:

• Choose a trigger, such as a new row in Google Sheets, a new record in Airtable, or an incoming webhook.
• Add the image automation module and select the Create a Render action.
• Connect your account with your API key, then pick the template you want to use.

The module can also list your templates and retrieve render status, so you can build more advanced flows when needed.

Mapping your data

Once you select a template, Make shows its layers as fields. You map values from the trigger into those fields, for example placing a product name into a title layer and a photo into an image layer. Each time the scenario runs, the module fills the template with that record's data.

Using the result

The module returns the URL of the rendered file. You can pass that URL to later modules in the same scenario, such as sending an email, posting to Slack, or saving to storage. This turns the scenario into a complete image pipeline.

Triggers and events

Because Make connects to thousands of apps, almost any event can start a render. Common triggers include new spreadsheet rows, new form submissions, new orders, and webhooks from your own systems, so images are created automatically as your data changes.

A common example

A frequent setup watches a spreadsheet or database for new records and generates an on-brand image for each one, keeping your visuals in sync with your data without manual work.