# How to generate visuals with Make

> Render images, PDFs, and videos from your Orshot templates in a Make scenario — import a ready-made workflow or build it yourself

- **URL**: https://orshot.com/help/generate-images-with-make

---

Make (formerly Integromat) builds visual automation **scenarios**. A scenario can render an **image, PDF, or video** from your Orshot template — and Orshot gives you a ready-made workflow to import, so you're running in about a minute. Here's the template we'll automate:

![The Orshot template we'll render from Make](https://orshot.com/help/automations/make-output.webp)

## 1. Know your template's parameters

Open your template in **Orshot Studio** and press **⌘]** (Toggle Parameter View). Every editable element is labelled with its **parameter** name — `headline`, `hero_food_photo`, `brand_name`, and so on. These are the values you'll set from Make. Any element can be made dynamic — see [Make your template dynamic](https://orshot.com/help/make-your-template-dynamic).

![The template in Orshot Studio with parameter labels turned on](https://orshot.com/help/automations/make-studio-params.webp)

## 2. Grab the ready-made workflow

On the template's card, click **Connect**, then open the **Make** tab. You'll find your **Template ID**, **API key**, and — under *Skip manual setup* — a **Copy Make workflow** button and a **Download Make .json** file. New to API keys? See [Find your API key and template ID](https://orshot.com/help/find-your-api-key-and-template-id).

![The Quick Connect sheet on the Make tab, with Copy and Download workflow options](https://orshot.com/help/automations/make-connect.webp)

## 3. Import the workflow into Make

In Make, create a new scenario. Open the **⋯** menu (top-right) and choose **Import blueprint**, then drop in the `.json` you downloaded (or paste the copied workflow).

![The ⋯ menu open with Import blueprint highlighted](https://orshot.com/help/automations/make-import-menu.webp)

## 4. Your scenario is ready

The blueprint loads a scenario that already calls Orshot's render endpoint with your template and its modifications — no wiring required.

![The imported scenario with the Orshot render module](https://orshot.com/help/automations/make-scenario.webp)

## 5. Prefer to build it yourself?

You can also add the step by hand: add a module, pick **Orshot → Generate Image from Studio Template**, and fill in the fields:

- **Connection** — your Orshot account (added once with your API key).
- **Template** — pick the template to render; its parameters appear as fields you can fill or map.
- **Response Type** — `URL` (easiest to use downstream), `Base64`, or `Binary`.
- **Image Format** — `png`, `jpg`, `webp`, `pdf`, or `mp4`/`webm`/`gif` for animated templates.
- **Scale** — `1` for the template's size, `2` for 2× resolution.

![The Orshot module configuration in Make](https://orshot.com/help/automations/make-config.webp)

## 6. Run it

Click **Run once**. Orshot renders your template with its modifications and returns the result — a hosted URL when **Response Type** is `URL`. With the format set to `gif`/`mp4`, an **animated** template returns video:

![The same template rendered as a short animation](https://orshot.com/help/automations/make-animated.webp)

## 7. Use it downstream

Add more modules after Orshot and pass the returned image along — upload it to Google Drive, post it to a channel, attach it to an email — then turn the scenario on to run it on a schedule or trigger.

## Related