Resources · Zapier integration

Nanonets OCR Zapier integrationAutomate Nanonets OCR with Zapier.

The Nanonets OCR Zapier integration gives you 3 triggers and 4 actions, with no search step. The actions send a file to be read, the triggers pick up the results. Here is what each one does, what it costs, and why some results arrive through a second Zap.

See the 7 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Nanonets OCR Zapier integration actually does

Nanonets OCR reads documents and images and pulls the information out of them, so text locked in a scan or a photo becomes data you can use. On Zapier it works both ways: an action hands a file to Nanonets for reading, and a trigger tells your other apps when a new result, called a prediction, is ready.

Three results come back often. Text out of every file you collect: OCR With File sends a document that lands in another app to Nanonets, so it gets read without anyone opening it. Tables kept as tables: OCR With File (Tables Included) and its document-level variant also extract the line items of a table, not just the running text. Results that land where your team works: New Prediction With Tables can push each finished reading into a spreadsheet, row after row.

What Zapier does not do for Nanonets OCR matters just as much. None of the 3 triggers is instant: Zapier checks on a timer, and that timer depends on your plan. Three of the four actions say their results appear later through a trigger, so the reading is collected by a second Zap; which of the 3 triggers brings it back is something to confirm at test. There is no search step either, and nothing uploaded before a Zap goes live is picked up.

If you are still weighing tools, see our Make vs Zapier comparison or our Zapier review.

Vocabulary

Zapier words you will meet on this page

Eight terms, one line each. They come back in every block below.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event and nothing else.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling trigger
A trigger Zapier checks on a timer, keeping only items it has not seen yet. All 3 Nanonets OCR triggers work this way.
Filter
A step that lets the Zap carry on only when what arrived meets a condition you set, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
Connection
Your Nanonets OCR account linked to Zapier once, then reused by every step of every Zap that touches it.
Cost

What a Nanonets OCR Zap really costs

Zapier bills tasks, not checks. The trigger never costs anything, however often Zapier looks for new predictions.

  • Tasks on the free plan100 per month
  • Zaps on the free planUnlimited, two steps each
  • Cost of a trigger check0 tasks
  • Premium appNo, free plan works

Each action that goes through counts as one task, so sending a file to Nanonets costs one task, and a three-action Zap uses three times what a one-action Zap uses. An action that fails is not counted. Nanonets OCR is not a premium app, so it works on the free plan, but that plan stops at two-step Zaps: one trigger, one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. When results arrive through a trigger, the reading takes two Zaps, one to send and one to collect, each with its own tasks. The grid below is how often Zapier checks the 3 polling triggers.

Connect

Connect Nanonets OCR to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, open Apps and click + Add connection. You need an account on Nanonets OCR, plus read or write access on anything you do not own yourself and want the Zap to touch.

  2. 02

    Pick Nanonets OCR

    Type Nanonets in the search box of the dialog, select Nanonets OCR in the results, then click Add connection. A new browser tab opens so you can sign in.

  3. 03

    Sign in and grant access

    Sign in to Nanonets OCR in that tab and grant Zapier access to the account. The connection is saved once and offered to every Zap step that uses Nanonets OCR.

First Zap

Your first Nanonets OCR Zap: log every document reading

GoalEach new document-level prediction in Nanonets OCR becomes a row in your spreadsheet, and your team chat hears about it.

  1. 01

    Create the Zap

    Start a new Zap and pick Nanonets OCR as the app that starts it. Choose New Prediction by Document as the event, then select your connection.

  2. 02

    Set the trigger

    Fill in the Application ID the trigger asks for. Testing brings back the three most recent predictions of the account, so you map the next steps on a real one.

  3. 03

    Add the row

    Add your spreadsheet as the action and pick the columns to fill. Check at test what the prediction actually carries before you map it into them.

  4. 04

    Tell the team

    Add your chat app as a third step. Three steps make this a multi-step Zap, so it needs a paid plan; on the free plan, stop after the spreadsheet row.

  5. 05

    Test, then publish

    Run each step once and read what came back. When the row shows up in your spreadsheet, click Publish to switch the Zap on.

Triggers

Nanonets OCR triggers on Zapier

3 events start a Zap when something happens in Nanonets OCR. Zapier checks for them at the interval your plan allows.

1

New Prediction

Polling trigger

In Zapier“Triggers when a new image is uploaded for prediction.”

When an image is uploaded to Nanonets for prediction, this trigger starts the Zap; check at test what each prediction carries. It is the plain version of the three, with nothing in its name about tables or documents.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when an OCR action said its results appear through a trigger and the test confirms they arrive here.
Watch out
the Application ID is required, and only uploads made after the Zap is published come through.
2

New Prediction by Document

Polling trigger

In Zapier“Triggers when a new document is uploaded for prediction.”

Here the unit is the document rather than the image: each new document uploaded for prediction starts the Zap once, and the test shows how the result is laid out.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when each document should give one row or one message in the next tool.
Watch out
the Application ID is required here too; check at test how the result of a long document is laid out.
3

New Prediction With Tables

Polling trigger

In Zapier“Triggers when a new image is uploaded for prediction.”

Like the plain image trigger, this one fires on a new image uploaded for prediction, but it is the one to pick when the reading includes tables you want to keep.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
when the files you send hold line items and the next step should receive them, for example rows of a spreadsheet.
Watch out
the Application ID is required, and images uploaded before the Zap was published never come through.
Actions

Nanonets OCR actions on Zapier

Nanonets OCR gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

OCR With File (Asynchronous)

Action

In Zapier“Uses Nanonets OCR to extract text asynchronously. Results will appear via the trigger”

Hands a file to Nanonets for reading and does not wait for the text: the result shows up later through a trigger. The Zap that sends and the Zap that collects are two separate Zaps.

When to use it
when you are fine collecting the text in a second Zap rather than in the one that sends the file.
Watch out
nothing comes back in this Zap, so plan the second one before you rely on it.
2

OCR With File (Tables Included) - Document Level Response

Action

In Zapier“Uses Nanonets OCR to extract text including line items. Results will appear via the trigger”

Reads a file with its tables and returns the result at the level of the whole document. Zapier highlights this one on the app page, and its results also come back through a trigger.

When to use it
when each document should come back as one result, tables included.
Watch out
the Application ID is required; pair it with a trigger Zap to collect what it reads.
3

OCR With File (Tables Included)

Action

In Zapier“Uses Nanonets OCR to extract text including line items. Results will appear via the trigger”

This one reads a file and asks for the line items of its tables too, not only the text around them. Like the asynchronous action, its results arrive later through a trigger.

When to use it
when the documents you process carry tables whose rows matter.
Watch out
the Application ID is required, and the text is collected by a trigger in another Zap.
4

OCR With File

Action

In Zapier“Uses Nanonets OCR to extract text”

Sends a file to Nanonets so its text gets extracted. Unlike the three other reading actions, its description says nothing about results coming back through a trigger.

When to use it
when a document lands in another app and you only need its text, without tables.
Watch out
the Application ID is required; check at test what comes back before you map it.
When it breaks

When a Nanonets OCR Zap breaks

Zapier lists no limit of its own for Nanonets OCR. The cases below are the general ones, and they apply to every Nanonets OCR Zap.

If a Zap stops doing what you expect, check these four cases first. For anything else, see our Zapier troubleshooting guide.

  • No catch-up on old files

    A Zap only reacts to what happens after you switch it on. Files uploaded before are never picked up; moving that backlog is a separate job.

  • A Zap that feeds itself

    A Zap that writes into the very place its own trigger watches can set itself off again and again, and burn through the task count.

  • Flood protection on big batches

    If a trigger suddenly returns a huge batch, after a bulk upload or a migration, Zapier's flood protection can hold it back.

  • The same prediction, never twice

    Zapier keeps track of what a polling trigger has already seen, so the same prediction does not start the Zap twice.
Need help

Need help automating Nanonets OCR with Zapier?

A person reads every message.

FAQ

Nanonets OCR Zapier integration: your questions

01Is the Nanonets OCR Zapier integration free?
Yes. Nanonets OCR is not a premium app, so its 7 operations work on the free Zapier plan. That plan gives you 100 tasks a month and an unlimited number of Zaps, each limited to two steps: one trigger and one action. Sending a file from another app to Nanonets fits that limit, and so does collecting a prediction into one other app. A filter or a second action needs a paid plan.
02How many tasks does a Nanonets OCR Zap use?
One task per action that succeeds, nothing for the trigger. Zapier can check for new predictions as often as your plan allows without spending a task. Sending one file with an OCR action costs one task; collecting the result into a spreadsheet costs one more, in a second Zap when the result arrives through a trigger. An action that fails is not counted against your plan, so only completed steps are billed.
03Does Nanonets OCR trigger Zaps in real time?
No. The 3 triggers, New Prediction, New Prediction by Document and New Prediction With Tables, are polling triggers: Zapier asks Nanonets for new predictions at a fixed interval. That interval depends on your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. On paid plans the interval can be changed, and a check can be run by hand from the editor while you test. Each trigger shows its interval on the app page.
04What does it take to connect Nanonets OCR to Zapier?
An account on Nanonets OCR, plus read or write access on anything you do not own yourself and want the Zap to touch. You add the connection from the Apps page of Zapier, sign in to Nanonets in the tab that opens and grant access. Every trigger and action then asks for an Application ID, a required field, so have that value ready before you build. Fill it in before each test.
05Why does the asynchronous Nanonets OCR action not return any text?
Because, by its description, the result appears later through a trigger rather than inside the Zap that sent the file. The two Tables Included actions say the same. So plan a second Zap that starts on a Nanonets OCR trigger, run a reading, then test that trigger to check that the result really arrives there before you map it anywhere. Which of the 3 triggers brings it back is not stated, so the test decides. OCR With File, the fourth action, says nothing of the kind.
06What if a Nanonets OCR operation is missing from Zapier?
Then the integration cannot do it today, whatever Zap you build. The Nanonets OCR page on Zapier shows the current list of triggers and actions, so check it before you plan a workflow. Two Zaps may cover the gap: one sends the file with an OCR action, the other collects the prediction with a trigger and passes it on. Each extra action in a Zap makes it multi-step. The trigger always opens the Zap.
07Zapier, Make or n8n for Nanonets OCR?
Compare them on criteria, not on a winner. Coverage first: Nanonets OCR has 7 operations on Zapier, so check whether the other tool offers the same reading options. Timing next: the 3 triggers are polling, so the interval of your plan sets how fast a prediction is collected. Then billing: Zapier counts each successful action, and a reading collected through a trigger spans two Zaps, each with its own tasks. Test the same file in both before you commit.
Same platform

Other docs you might need on this stack.

Browse all integrations