Resources · Make integration

RenderForm Make integrationAutomate RenderForm with Make.

Need images and screenshots generated for you instead of by hand? The RenderForm Make integration gives you 6 modules: 4 actions and 2 searches. This page shows how to link your account, build a first scenario and pick the right module.

Try the RenderForm integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the RenderForm Make integration do?

The RenderForm Make integration lets a Make scenario, the automation you build as a chain of bricks, ask RenderForm to produce an image from one of your templates or a screenshot of a web page. Each brick is a module, and RenderForm brings six of them. There is no trigger in the set, so another app or a schedule starts the flow.

Visuals that follow your data. A marketing team keeps a template in RenderForm and lets a row from a spreadsheet or a form answer fill it in through Render an Image. Every new entry comes back as a finished picture, without anyone opening a design tool.

Proof that a page looked a certain way. Take a Screenshot captures a website on demand, which helps a support or QA team attach a visual record to a ticket at the moment something is reported.

A clear view of what was produced. Get Requests returns the images and screenshots already generated, and Get Templates lists the templates of your organization, so a scenario can pick the right design or report on past output.

What Make does not do here: react on its own to something happening inside RenderForm, because the app has no trigger. For any endpoint the six modules skip, Make an API Call reuses the same connection. The same app often has an n8n node too; the n8n vs Make comparison helps you weigh the two editors. To go further, the Make training covers scenario building step by step, and the Make troubleshooting guide helps when a run fails.

Connect

How do you connect RenderForm to Make?

  1. 01

    Copy your API key from RenderForm

    Log in to RenderForm, open the account section and click the API Keys tab. Copy the key shown there. You need an active RenderForm account for this; the key is what lets Make act on your behalf.

  2. 02

    Add a RenderForm module in Make

    In your Make scenario, add any RenderForm module and click Create a connection. A connection is your RenderForm account linked to Make once, then reused by every RenderForm module you add later.

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied, follow the on-screen instructions and save. The module can now render images and screenshots with your account.

First scenario

Your first scenario with RenderForm

GoalWhen new data lands in another app, Make fills a RenderForm template and returns the finished image.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Start with the app that holds your data, such as a form or a spreadsheet, since RenderForm has no trigger of its own.

  2. 02

    Add Render an Image

    Click the + to the right of that first module, search for RenderForm and pick Render an Image. Choose your connection, or click Create a connection if you have not linked the account yet.

  3. 03

    Map your data into the template

    Fill the module with values mapped from the previous module. Each bundle, meaning one item passed from a module to the next, becomes one image, so one form answer gives one picture.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open the bubbles above each module to read the bundles it received and check that the image came back as expected.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Then switch the scenario on so Make keeps producing images without you.

Modules

What can RenderForm do in Make?

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

RenderForm1

Deprecated: Render an Image

Action

In Make“Generates an image based on provided template.”

This is the older version of the image module, still listed so existing scenarios keep running. It builds a picture from one of your templates, like its successor.

When to use it
only when you maintain a scenario that already relies on it and you are not ready to rebuild that step.
Watch out
Make marks it as deprecated, so a new scenario is better started on Render an Image instead.
RenderForm2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

You get a way to reach any RenderForm endpoint that the listed modules do not cover, using the connection you already set up. No new credentials to paste.

When to use it
when your process needs a RenderForm feature that none of the five other modules exposes.
Watch out
you describe the request yourself, so keep the RenderForm API documentation open while you set it up.
RenderForm3

Render an Image

Action

In Make“Generates an image based on provided template.”

You hand it a template and data, and it gives back a finished image. This is the current module for turning a row, an order or a form answer into a visual.

When to use it
a new product listing needs its own banner, or a new registration deserves a personal badge.
Watch out
each incoming bundle produces its own image, so a long list of rows means one render per row and as many operations.
RenderForm4

Take a Screenshot

Action

In Make“Takes a screenshot of given website.”

Give it a website address and it returns a picture of that page as it stands at the moment the scenario runs. Handy as visual evidence without opening a browser.

When to use it
when a ticket or a report should carry an image of the page it talks about, captured the instant the record is created.
Watch out
every page you capture counts as one operation, meaning one run of a module that Make bills on your plan, so feed it only the records that need a picture.
RenderForm5

Get Requests

Search

In Make“Returns generated images and screenshots.”

This search brings back the images and screenshots RenderForm has already generated, so you can reuse or report on past output instead of rendering again.

When to use it
to send a recap of what was produced, or to find an earlier image before creating a duplicate.
Watch out
a search can return zero, one or many bundles, and every module placed after it runs once per result.
RenderForm6

Get Templates

Search

In Make“Returns templates of your organization.”

You receive the list of templates that belong to your RenderForm organization, which lets a scenario choose a design by itself rather than relying on a hard-coded one.

When to use it
when several teams keep their own designs and the scenario must pick the right one before rendering.
Watch out
as a search, it returns one bundle per template, and whatever comes after it runs once for each of them.
Need help

Need help automating RenderForm with Make?

A person reads every message.

FAQ

RenderForm and Make: frequently asked questions

01Is the RenderForm Make integration free?
Yes, on the Make side. RenderForm is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes of execution and files up to 5 MB, with 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. You still need an active RenderForm account with an API key; its subscription is set by RenderForm, not by Make.
02What do you need to connect RenderForm to Make?
Two things: an active RenderForm account and its API key. Log in to RenderForm, open the account section, click the API Keys tab and copy the key. In Make, add any RenderForm module, click Create a connection, give it a name if you want and paste the key. That single connection then serves all six RenderForm modules in your scenarios, so you only do this once per account, not once per scenario.
03Can a RenderForm scenario start in real time?
Not from RenderForm itself, because the app has no trigger in Make. The scenario starts either on a schedule, every 15 minutes by default and down to 1 minute on paid plans, or from a trigger of another app placed first, for example a form or a spreadsheet. If that other app offers an instant trigger, the one with the lightning badge, it calls Make through a webhook as soon as something happens, and RenderForm renders right after.
04What if the RenderForm module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the RenderForm API with the connection you already created, so a feature absent from the listed modules stays within reach. You write the request yourself, which asks for a look at the RenderForm API documentation. The Make documentation for this app also warns that its content is generated from vendor material and may contain mistakes, so check important details with RenderForm directly.
05Should you use Make or n8n for RenderForm?
It depends on the editor your team already uses. On Make, RenderForm offers six modules, including Render an Image, Take a Screenshot and Make an API Call for anything else, and the app runs on the Free plan. The same app often has an n8n node as well. Compare what each side exposes for your exact process, check the modules you need exist, then pick the tool where the rest of your automations already live.
Same platform

Other docs you might need on this stack.

Browse all integrations