Resources · Make integration

Orshot Make integrationAutomate Orshot with Make.

Can Make turn fresh data into finished Orshot images on its own? The Orshot Make integration gives you 5 modules: 3 actions and 2 searches. It suits marketers and ops teams who already design in Orshot, and this guide takes you from the API key to a first scenario that works.

Try the Orshot integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Orshot Make integration let you automate?

The Orshot Make integration links your Orshot account to Make, a tool where you build a scenario: an automation made of modules, each one a brick that acts in one app. Here, those bricks fill an Orshot template with data coming from somewhere else and hand back a finished image, with no code and no design tool open.

A product card for every new catalog item. An online shop adds a product in its store app, Make passes the name and photo to Generate Image from Studio Template, and the card comes out in the shop's own layout, ready for the next module to store or post.

A social visual without a template of your own. A small agency starting out can pick a ready design with List Library Templates, then feed it with Generate Image from a Library Template each time a new blog post is published. It is the quickest way to see the whole chain working.

The right template for each brand. When you run several brands, List Studio Templates brings back your custom designs so the scenario can choose among them before rendering.

What the page cannot promise: Orshot's module documentation on Make is short and flagged by Make as AI-generated from the vendor's docs, so check anything important directly with Orshot. For endpoints without a dedicated module, Make an API Call fills the gap. If you are weighing tools, the n8n vs Make comparison lays out the criteria, the Make pricing page explains how operations are billed, and the Make training helps you go further on your own.

Connect

How do you connect your Orshot account to Make?

  1. 01

    Copy your Orshot API key

    Log in to Orshot and open the API Keys section from the sidebar. Copy the key shown on that page. You need an active Orshot account for this; without one, the key does not exist yet.

  2. 02

    Add an Orshot module in Make

    In your scenario, add any Orshot module, then click Create a connection. A connection is your Orshot account linked to Make once, and every Orshot module reuses it afterwards.

  3. 03

    Paste the key and save

    Give the connection a name in the Connection name field if you like; it is optional but helps when you have several accounts. Paste the API key, follow the on-screen instructions, and save.

First scenario

Build your first scenario with Orshot

GoalWhen a new record reaches the app that feeds your scenario, Make fills your Orshot Studio template and produces the image.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to place the first module. That module decides when everything starts.

  2. 02

    Start from the app holding your data

    Orshot has no trigger, so the first module belongs to the app where your records live, such as a sheet or a CRM. Each new record it sends on is a bundle: one item passed to the next module.

  3. 03

    Add Generate Image from Studio Template

    Click the + on the right of the first module, search for Orshot, pick Generate Image from Studio Template and choose the connection you created earlier.

  4. 04

    Pick the template and map the data

    Once connected, Make lists what it can read in your account. Select your template, then drag the values from the first module into the template's parameters.

  5. 05

    Test with Run once

    Click Run once to execute the scenario a single time. Read the bundles each module received and check the image came out as expected.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module; a new scenario checks every 15 minutes by default. Then switch the scenario on, and it keeps producing images without you.

Modules

What each Orshot module does

Orshot gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Orshot1

Generate Image from a Library Template

Action

In Make“Generate an image from Orshot Library Template”

Fills one of the ready-made designs from Orshot's public library with the data your scenario carries and gives you a finished image, without drawing anything yourself.

When to use it
you have not designed a template of your own yet and want a working scenario first, for instance a quote card for each new blog post.
Watch out
each image counts as one operation (one module run on one bundle, what Make bills), so a batch of many bundles uses just as many.
Orshot2

Generate Image from Studio Template

Action

In Make“Generate an image from a Studio Template”

Renders an image from a template you built yourself in Orshot Studio, so every output keeps your brand's layout while the text or picture changes from one bundle to the next.

When to use it
a new product enters your catalog and its promo visual should be ready without opening a design tool.
Watch out
design and save the template in Studio first; this module works from what already exists in your account.
Orshot3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of Orshot's API from your scenario with the connection you already set up, so you are not stuck when the four other modules stop short.

When to use it
the action you need exists in Orshot's API but has no dedicated module in Make.
Watch out
you will need Orshot's own API documentation to know what to call, so reach for a dedicated module whenever one covers your case.
Orshot4

List Library Templates

Search

In Make“Retrieve all available templates from Orshot's public library”

Brings back the designs available in Orshot's public library, one bundle per template, so you see what exists before choosing one to render from.

When to use it
while setting things up, to browse the library from inside Make and note the template that suits your campaign.
Watch out
a search can return zero, one or many bundles, and the next module runs once per bundle, which multiplies operations.
Orshot5

List Studio Templates

Search

In Make“Retrieve all your custom templates created with Orshot Studio”

Retrieves the custom templates you created in Orshot Studio, which lets a scenario pick the right design on the fly instead of relying on one fixed choice.

When to use it
you handle several brands or campaigns and each record should land in its own template before rendering.
Watch out
if one template is always enough, skip this search; it adds an operation to every run without changing the result.
Need help

Need help automating Orshot with Make?

A person reads every message.

FAQ

Questions about Orshot and Make

01Is the Orshot Make integration free?
Yes, on Make's side. Orshot is a standard app, so it works from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations: one module running on one bundle. Orshot itself requires an active account; check its own pricing page for that part.
02What do you need to connect Orshot to Make?
An active Orshot account and its API key. You find the key in the API Keys section of the Orshot sidebar and copy it from there. In Make, add any Orshot module, click Create a connection, name it if you want, and paste the key. That single connection then serves all 5 Orshot modules, so you only do this once per Orshot account. No webhook is involved, because Orshot has no instant module.
03Does Orshot trigger scenarios in real time in Make?
No, because Orshot has no trigger in Make at all. Your scenario starts elsewhere: either on a trigger from the app that holds your data, such as a spreadsheet or a CRM, or on Make's own schedule, which runs a new scenario every 15 minutes by default, and at the shortest every 15 minutes on the Free plan or every minute on paid plans. Orshot then comes in as the second module, rendering the image from what the first one passed along.
04What if the Orshot module you need is missing?
Use Make an API Call. It calls any endpoint of Orshot's API with the connection you already have, which covers what the 3 actions and 2 searches do not. You will need Orshot's API documentation to know which call to make. Also keep in mind that Make marks its Orshot documentation as AI-generated from the vendor's docs, so if a detail matters, confirm it with Orshot directly before building around it.
05Should you use Make or n8n for Orshot?
It depends on the tool your team already uses. On Make, Orshot is a standard app with 5 modules, including Make an API Call for anything else, and it runs on the Free plan. The same app often has a node on n8n too, so it is worth checking there before choosing. Neither answer is right for everyone: compare how each tool fits your existing scenarios, your skills and your budget, then decide where your image automations should live.
Same platform

Other docs you might need on this stack.

Browse all integrations