Resources · Zapier integration

Base64.ai Zapier integrationAutomate Base64.ai with Zapier.

The Base64.ai Zapier integration gives you 2 actions, 0 triggers and 0 searches. Both actions read a document and pull out its text, photos and signatures. Here is how to feed them, what a scan costs on your plan, and where people get stuck.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Base64.ai Zapier integration does, and what it does not

Base64.ai reads documents for you, of any type: an image, a PDF, a zip archive or an office file. It extracts the text, the pictures and the signatures, whatever the format. Plugged into Zapier, it becomes a reading step inside an automation: another app hands over a file, Base64.ai scans it, and the next step stores or sends what came out.

Three jobs it handles well. Inbox to data: a supplier sends a PDF, Scan a Document by URL reads it from its link, and what it extracted lands in your spreadsheet instead of being typed by hand. Forms that arrive as raw files: some tools pass a document as a long encoded string rather than a link, and Scan a Document by Bytes takes it as is. A paper trail you can search: every contract or receipt dropped in a shared folder gets read once, and its content follows into your CRM or your archive.

Now the limits. Base64.ai has no trigger on Zapier, so it can never start a Zap by itself: another app always goes first. It has no search either, so you cannot look up a past scan from a Zap. And nothing in the source documents a rate limit, a page limit or a list of returned fields, so run a few real documents before you trust the output.

Choosing between platforms? The n8n vs Zapier and Make vs Zapier comparisons set out the criteria, and the Zapier review covers the tool as a whole.

Vocabulary

Six Zapier words before you start

Six terms carry the rest of this page. Plain definitions, no jargon.

Zap
Your automation on Zapier: one starting event, followed by one or more steps that run each time that event happens.
Trigger
The event that sets the Zap off. Base64.ai has none, so here it always comes from another app, such as a storage tool.
Action
What the Zap does once it starts: the step that writes, sends or reads something for you, here a document scan.
Task
What Zapier bills you for: one action that completes successfully. Your plan sets how many you get each month.
Polling vs instant
A polling trigger is checked on a timer, an instant one is pushed by the app the moment it happens. It sets how fast your scan starts.
Filter
A step that lets the Zap continue only if the incoming data matches your rule, for example only PDF files.
Cost

What scanning documents through Zapier costs

Base64.ai is not a premium app, so it is available on the free plan. Zapier counts tasks, nothing else.

  • Free plan100 tasks per month, unlimited Zaps, two steps per Zap
  • Premium appNo, Base64.ai works on the free plan
  • One scanOne task when it succeeds, zero when it fails
  • Scan then saveTwo actions, so a paid plan and two tasks per file

Every scan that succeeds is one task. The trigger of the other app is free, and so is all the waiting in between. A scan that fails is not counted. Watch the step count, though: the free plan only builds two steps, one trigger and one action. A Zap that scans and then writes the result somewhere has two actions, so it is a multi-step Zap and needs a paid plan, and it costs two tasks per document. How fast the scan starts depends on the trigger you pick, following the grid below when it is a polling one.

Connect

Link your Base64.ai account to Zapier

  1. 01

    Start from Apps

    Open the Apps page of your Zapier account and click + Add connection. That connection is your Base64.ai account, linked once and then reused by every Zap that scans a document.

  2. 02

    Select Base64.ai

    Search for Base64.ai in the dialog, pick it, then click Add connection. Zapier opens a separate tab where Base64.ai asks you to identify yourself before going on.

  3. 03

    Sign in and allow access

    Log into your Base64.ai account in that tab and let Zapier use it. You need your own account, plus access to any file you do not own but want the Zap to send for scanning.

First Zap

Your first Base64.ai Zap, step by step

GoalEvery time a supplier invoice lands in a shared folder, have Base64.ai read it and log what it found in a spreadsheet.

  1. 01

    Choose the starting app

    Create a Zap and pick the storage tool where invoices arrive, with its new file event. Base64.ai cannot start a Zap, so this step always comes from elsewhere.

  2. 02

    Test with a real invoice

    Run the trigger test. Zapier brings back the three most recent items, so drop a real invoice in the folder first and pick it.

  3. 03

    Let only PDFs through

    Add a Filter from the plus icon, choose the file name field, a text rule and the value .pdf, so stray images and other files stop here.

  4. 04

    Add the scan

    Pick Base64.ai and Scan a Document by URL, then map the file link into Document to scan. Test the step and read what came back.

  5. 05

    Save the result and publish

    Add the spreadsheet step, map the extracted values into its columns, test it, then click Publish to switch the Zap on for good.

Actions

The Base64.ai actions

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

1

Scan a Document by URL

Action

In Zapier“Scans a document that is provided by a URL or Hydrate File. File can be an image (jpeg, png etc.), PDF, zip or an office document (.doc, .docx, etc.).”

Reads a document from a link, or from a file passed by an earlier step, and returns its text, images and signatures. Images, PDFs, zip archives and office files are all accepted.

When to use it
the file already lives in a storage tool or an email attachment that Zapier can point to.
Watch out
the link must open for Base64.ai, so a private file with no access fails. Turn on Hide DOM if you only need the values, to keep the result lighter.
2

Scan a Document by Bytes

Action

In Zapier“Scans a document that is provided by a string of bytes (e.g. data:image/png;base64,iVBORw0KGgoAAAANSUhEU...). File can be an image (jpeg, png etc.), PDF, zip or an office document (.doc, .docx, etc.).”

Takes the document as a long string of encoded characters instead of a link, then extracts its content the same way.

When to use it
the previous app gives you the file only as raw data, as in the data:image example shown in the editor field.
Watch out
the field expects the full string, starting with its file type, as in the example shown in the editor. A cut string means a failed scan.
When it breaks

When a Base64.ai Zap breaks

Zapier attaches no help article to Base64.ai. The cases below come from how every Zap behaves, and they are the ones that catch people first.

When a scan Zap stops, the cause is usually upstream, in the app that hands over the file. Our Zapier troubleshooting page covers the general fixes.

  • Last month's invoices were never scanned

    A Zap only reacts to files that arrive after you switch it on. Everything already in the folder is skipped, and scanning that backlog is a separate job.

  • The scan result fills the watched folder

    If a later step saves the output in the folder your trigger watches, each saved file starts the Zap again and your tasks run out quickly.

  • A bulk upload gets paused

    Drop hundreds of documents at once and the trigger returns a huge batch. Zapier's flood protection can hold it back.

  • The same file is not scanned twice

    On a polling trigger, Zapier remembers the items it has already seen, so the same item never starts the Zap, and its scan, a second time.
Need help

Need help automating Base64.ai with Zapier?

A person reads every message.

FAQ

Base64.ai Zapier integration: common questions

01Is the Base64.ai Zapier integration free?
Yes, in its simplest form. Base64.ai is not a premium app, so the free plan covers it, with 100 tasks per month and unlimited Zaps. The limit is the step count: the free plan allows one trigger and one action. Since Base64.ai has no trigger of its own, a free Zap can scan a document but cannot then save the result in a second step. As soon as you want to store what was read, the Zap becomes multi-step and needs a paid plan.
02How many tasks does a Base64.ai scan use?
One task per successful scan. The trigger that brings the file in costs nothing, and a scan that fails is not billed. The bill grows with the actions after it: scan plus spreadsheet row is two tasks per document, add a notification and it is three. Checking for new files is free, however often it happens. A filter placed before the scan keeps you from paying for files you never wanted read, such as stray images.
03Does Base64.ai scan documents in real time?
It depends entirely on the app that starts the Zap, because Base64.ai has no trigger. If that app reports new files instantly, the scan runs straight away. If it uses polling, the scan waits for the next check, which is every 15 minutes on the free plan, 2 minutes on Professional and 1 minute on Team and Enterprise. In the editor, an instant trigger shows a lightning bolt, so you can tell before publishing.
04What do you need to connect Base64.ai to Zapier?
A Base64.ai account and access to the files you want scanned. In Zapier, open Apps, click + Add connection, search for Base64.ai, sign in on the tab that opens and grant access. The connection is created once and reused by every Zap. If the documents sit in a folder or mailbox that belongs to someone else, make sure you can read them, otherwise the trigger never passes them on and nothing reaches the scan.
05Should you scan by URL or by bytes?
Look at what the previous step gives you. If it provides a link to the file or the file itself, use Scan a Document by URL, which is the simpler of the two. If it only hands over the document as a long encoded string, use Scan a Document by Bytes and paste that string in full. Picking the wrong one makes the scan fail, so check the trigger output before choosing.
06What if the Base64.ai operation you need is not there?
Then the integration does not offer it today. On Zapier, Base64.ai exposes two scanning actions and nothing else: no trigger, no search, no way to fetch a past result. Many needs still fit, because a filter and the steps of other apps can sort and route what a scan returns. For anything beyond that, such as reacting to a finished scan inside Base64.ai, another route is needed, and that is the kind of build a Zapier agency handles.
07Zapier, Make or n8n for Base64.ai?
Pick by criteria, not by a ranking. Zapier gets you scanning fastest and Base64.ai works on its free plan, but saving the result already requires a paid plan. That matters when each document goes through several steps after the scan. Compare which Base64.ai operations each platform exposes, what one scanned document costs at your volume, and who will look after the automation over time. On Zapier, the scan always waits for the trigger of another app.
Same platform

Other docs you might need on this stack.

Browse all integrations