Resources · Make integration

Canvasflare Make integrationAutomate Canvasflare with Make.

Need website screenshots or rendered images without opening Canvasflare each time? The Canvasflare Make integration gives you 3 action modules. It suits marketers and ops teams, and this page takes you from the connection to a first working scenario.

Try the Canvasflare integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Canvasflare Make integration let you automate?

The Canvasflare Make integration links your Canvasflare account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules. A module is one brick of that chain. Canvasflare brings three of them, all actions: capture a website, render an image, or call its API directly.

Capture a page as soon as a link shows up. Another app hands Make a web address, say a form entry, and Screenshot a website takes the capture. Each item flowing through is a bundle, and each run of a module on a bundle is an operation, the unit Make counts on your plan.

Produce a visual inside the flow. Render an image creates a picture at that point of the scenario, so the following module can pick it up.

Reach what the two modules skip. Make an API Call calls any endpoint of the Canvasflare API with the connection you already set up.

One honest limit: Make's own documentation for Canvasflare is thin, because little public information exists about the app, so plan to test every module with Run once. The same app often has an n8n node as well; the n8n vs Make comparison lays out the criteria. New to the editor? The Make training covers the basics, and Make troubleshooting helps when a run fails.

Connect

How do you connect Canvasflare to Make?

  1. 01

    Add a Canvasflare module

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

  2. 02

    Name the connection

    Give the connection a name if you want. The field is optional, but a clear label saves you guesswork the day you link a second Canvasflare account and have to pick the right one.

  3. 03

    Authorize and save

    Make then either opens the Canvasflare authorization page or asks you to paste the key Canvasflare gives you. Finish that step, click Save, and the module can use your account.

First scenario

Build your first scenario with Canvasflare

GoalWhen a new link reaches Make from another app, Canvasflare takes a screenshot of that website.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Canvasflare has no trigger, so this first module comes from the app that holds your links, such as a form tool.

  2. 02

    Add Screenshot a website

    Click the + on the right of that first module, search for Canvasflare and pick Screenshot a website. Click Create a connection if your account is not linked yet.

  3. 03

    Map the web address

    Fill the module by mapping the link the first module received. Mapping means you pick a value from the previous module instead of typing it, so every new link gets its own capture.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time, and you can open each module to read the bundles it received and confirm the screenshot came back.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest gap between two scheduled runs.

Modules

What can each Canvasflare module do?

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

Canvasflare1

Make an API Call

ActionIn the docs only

This is your way into the whole Canvasflare API: any endpoint can be called from the scenario, using the connection you already created, so nothing needs to be set up twice.

When to use it
you need a Canvasflare option that neither Render an image nor Screenshot a website offers.
Watch out
you write the request yourself, so run it once and read the returned bundle before switching the scenario on.
Canvasflare2

Render an image

ActionIn the docs only

You get an image produced by Canvasflare right inside your scenario, ready for the next module to store or send. As the name says, it creates a picture rather than reading one.

When to use it
a record arriving from another app should end up as a visual at this point of the flow.
Watch out
Make's documentation does not describe this module's settings, so inspect its output with Run once before building on it.
Canvasflare3

Screenshot a website

ActionIn the docs only

You receive a capture of a web page without opening a browser: the module takes the address you pass it and hands the screenshot to whatever comes next.

When to use it
links arrive from a form or a spreadsheet and you want a visual record of each page.
Watch out
every capture is one operation, so a scenario that receives a long list of links spends operations quickly.
Need help

Need help automating Canvasflare with Make?

A person reads every message.

FAQ

Canvasflare and Make: common questions

01Is the Canvasflare Make integration free?
Yes. Canvasflare is a standard app, so it works from the Make Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and allow 40 minutes of execution. Usage is counted in credits, meaning operations. Canvasflare's own pricing is a separate matter and is not covered here.
02What is needed to connect Canvasflare to Make?
A Canvasflare account and a Make account. Make's documentation lists no specific prerequisite for this app. Add a Canvasflare module, click Create a connection, name it if you want, then either authorize Make on the Canvasflare page or paste the key Canvasflare provides, and click Save. The connection is made once and reused by every Canvasflare module. Since the documentation for Canvasflare is limited, test the connection straight away with Run once on a simple scenario.
03Does the Canvasflare Make integration react in real time?
It depends on what starts the scenario, because Canvasflare has no trigger of its own: its 3 modules are actions. Start the scenario from another app's trigger. An instant trigger is called by that app through a webhook as soon as something happens, while a scheduled trigger is checked on the scenario's schedule. You can also run the scenario on a plain schedule, every 15 minutes by default, down to 1 minute on a paid plan.
04What if a Canvasflare module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Canvasflare API from your scenario with the connection you already have, so you are not limited to Render an image and Screenshot a website. Keep in mind that Make's documentation for Canvasflare is limited, since little public information exists about the app. Check each request with Run once and read the bundle it returns before you switch the scenario on.
05Should you use Make or n8n for Canvasflare?
It depends on the tool your team already works with. In Make, Canvasflare offers 3 modules: Render an image, Screenshot a website and Make an API Call for the rest of the API. The same app often has an n8n node too, so look at where your other scenarios already live before choosing. Make gives you a visual editor, Run once testing and a Free plan to try the integration. If your team already builds in n8n, stay there; if not, a first test in Make costs you nothing.
Same platform

Other docs you might need on this stack.

Browse all integrations