Resources · Make integration

Base64.ai Make integrationAutomate Base64.ai with Make.

Can Make hand your documents to Base64.ai for scanning, with no code at all? Yes. The Base64.ai Make integration gives you 3 action modules: scan a file, scan a link, or call the API directly. This page shows how to connect your account and build a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Base64.ai Make integration do for you?

The Base64.ai Make integration lets a Make scenario (the automation you build, a chain of steps) send documents to Base64.ai for scanning. Each step is a module, and this app brings 3 of them, all actions. Nothing starts on the Base64.ai side: the scenario begins with another app or on a schedule, then passes the document along.

Scan supplier invoices already moving through your scenario. When a previous module already holds the file itself, such as an attachment picked up by a storage or email app, Scan a Document by File Binary takes that file and sends it to Base64.ai. An accounting team can route every supplier invoice through the scan without anyone opening it first.

Scan documents that only exist as links. Some tools hand you a web address rather than a file. Scan a Document by URL works from that address, so a form submission that includes an uploaded contract can go straight to scanning.

Reach the rest of the API. Make an API Call reuses the same connection to call any Base64.ai endpoint the two scan modules leave out.

One honest limit: Make states that its own documentation for Base64.ai is limited because too little public information exists about the app. Run once, the editor's test button, is therefore your best guide to what each module returns. If a step fails, the Make troubleshooting guide helps you read the error. Weighing tools first? The n8n vs Make comparison and the Make pricing breakdown cover the basics.

Connect

How do you connect Base64.ai to Make?

  1. 01

    Add a Base64.ai module

    In your scenario, click the + and search for Base64.ai, then pick any of its modules. Make asks for a connection (your Base64.ai account linked to Make once, then reused by every Base64.ai module), so click Create a connection.

  2. 02

    Name it and authorize

    Give the connection a name if you like, which helps when several accounts coexist. Then follow what the window asks for: either you approve Make on the Base64.ai page, or you paste the key Base64.ai gives you.

  3. 03

    Save and check

    Click Save. The connection now appears in the module, and every other Base64.ai module in any scenario can pick it from the list instead of asking again.

First scenario

Build your first Base64.ai scenario

GoalWhen another app hands your scenario a document link, Make sends it to Base64.ai for scanning.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Base64.ai has no trigger, pick the app where your document links come from.

  2. 02

    Set up the source module

    Connect that app and fill its fields. Once the connection exists, Make lists what it can read there, so you choose from menus rather than typing paths.

  3. 03

    Add Scan a Document by URL

    Click the + to the right of the first module, search Base64.ai and pick Scan a Document by URL. Create the connection, then map the link from the previous module into it.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time; click each module to read the bundles it received, a bundle being one item passed from step to step, here one document.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and turn the scenario on. From then on each new link goes to Base64.ai without you touching it.

Modules

The 3 Base64.ai modules in Make

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

Base64.ai1

Make an API Call

ActionIn the docs only

You get access to any Base64.ai endpoint from inside a scenario, through the connection you already created, with no second login to manage.

When to use it
a feature you need in Base64.ai has no dedicated module here, since only the two scan modules exist besides this one.
Watch out
you have to know the endpoint you are calling, and Make's documentation for this app is limited, so test each call with Run once.
Base64.ai2

Scan a Document by File Binary

ActionIn the docs only

Hand Base64.ai the file itself, taken from an earlier module, and the scan result comes back into your scenario for the following steps to use.

When to use it
the document already travels through the scenario as a file, for example an invoice attachment fetched by a mail or storage module.
Watch out
the Free plan caps files at 5 MB, so large scanned PDFs may need a paid plan.
Base64.ai3

Scan a Document by URL

ActionIn the docs only

Point Base64.ai at a web address and it scans the document found there, so you skip downloading the file into the scenario first.

When to use it
your source app gives you a link, like a form tool that stores uploads online, rather than the file content.
Watch out
the link has to be reachable by Base64.ai; a private address that needs a login on your side is a likely cause of failure, so check it in Run once.
Need help

Need help automating Base64.ai with Make?

A person reads every message.

FAQ

Base64.ai and Make: common questions

01Is the Base64.ai Make integration free?
Yes, on the Make side. Base64.ai is a standard app, available from the Free plan onward, like the 3,000+ standard apps. The Free plan allows 2 active scenarios, runs of up to 5 minutes, files up to 5 MB, 512 MB of data transfer, and at least 15 minutes between two scheduled runs. Make counts each operation, meaning one module run on one bundle, against your plan. Paid plans lower the interval to 1 minute. Your Base64.ai account is a separate matter that this page does not cover.
02What do you need to connect Base64.ai to Make?
A Base64.ai account and a Make account. Make's documentation lists no specific prerequisite for this app and gives no official connection steps, so the generic Make flow applies: add a Base64.ai module, click Create a connection, optionally name it, authorize Make on the Base64.ai page or paste the key the app provides, then click Save. That single connection serves all 3 modules, including Make an API Call. If the save fails, check the key or the approval before anything else.
03Can Base64.ai start a Make scenario in real time?
No, because Base64.ai has no trigger module in Make, only 3 actions. A scenario that uses it has to start elsewhere. Either you set a schedule on the first module, every 15 minutes by default and down to 1 minute on paid plans, or you open the scenario with an instant trigger from another app, one that calls Make through a webhook as soon as something happens. Base64.ai then works as the second step.
04What if a Base64.ai feature is missing from the Make modules?
Use Make an API Call. It is one of the 3 modules, and it can call any endpoint of the Base64.ai API with the same connection, so the two scan modules are not the ceiling. Keep in mind that Make says its documentation for Base64.ai is limited for lack of public information about the app. Rely on Base64.ai's own API reference for the endpoint, then confirm the response with Run once before you switch the scenario on.
05Should you use Make or n8n for Base64.ai?
It depends on the tool your team already runs. On Make, Base64.ai offers 3 modules: scanning by file, scanning by URL, and a direct API call, which covers the rest of the API. Many apps also have an n8n node, but this page does not confirm one for Base64.ai, so check the n8n catalog before choosing. If you already build in Make, the modules above are enough to start, and the comparison page linked earlier lays out the criteria side by side.