Nobody opens the file
A supplier invoice lands in your Google Drive folder, ParserBee reads it, and the invoice number, date and total appear as a new row in your spreadsheet. Nobody types anything.
Integration · Zapier app
ParserBee Zapier integration: the complete setup guide
Add the Extract Data From Document action to any Zap. Give it a link to a document and ParserBee returns the fields you asked for, ready to send to Google Sheets, Xero, QuickBooks, Slack or thousands of other apps.
No code About 10 minutes Thousands of apps
Extract Data From DocumentEvery field in the pickerTest on Zapier's free plan
Start with 25 free pages. No credit card. Stuck? Our team sets it up with you.
One action, two fields
Extract Data From Document takes a Template ID and a link to the document. It returns the fields your Parser Template asks for.
Every field ready to map
Each field ParserBee finds appears in Zapier's field picker, ready to drop into a column, a record or a message in the next step.
- How it connects
- Zapier app
- Set-up time
- About 10 minutes
- You need
- A Zapier account (multi-step Zaps need a paid plan)
- Best for
- Connecting to accounting tools, CRMs and chat without code
What you can build
A document arrives, ParserBee reads it, the data goes where you need it
The pattern is always the same three steps. Each of these is a Zap you can build in about ten minutes.
Google Drive
Google Sheets
Google SheetsInvoices to a spreadsheet
New file in Google Drive, extracted by ParserBee, added as a row in Google Sheets.
Google Drive or OneDriveXero or QuickBooks
Xero or QuickBooksInvoices into your accounting tool
New invoice in a folder, extracted by ParserBee, created as a bill in Xero or QuickBooks Online.
OneDriveWebhook
WebhookPurchase orders into your ERP
New file in OneDrive, extracted by ParserBee, posted to your internal system with a webhook.
Careers formAirtable
AirtableCVs into your hiring tracker
A candidate uploads a CV to your careers form. ParserBee pulls out name, email, skills and experience, and Zapier creates the Airtable record.
OneDriveAirtable
AirtableAny document into Airtable
New file in OneDrive, extracted by ParserBee, created as an Airtable record.
Cloud drive or formSlack
SlackDelivery notes into Slack
New file in your cloud drive or a form submission with a document, extracted by ParserBee, posted to Slack with the reference number and quantities.
Before you start
You need four things
All four take a few minutes to get.
- 1
A ParserBee account
The free trial includes 25 pages, which is plenty to test a Zap with. Create an account.
- 2
A Parser Template
Your list of fields: what you want pulled out of every document, written in plain English. Step 1 below.
- 3
Your ParserBee API key
This is how Zapier proves the request came from your account. Step 2 below.
- 4
A Zapier account
The free plan is enough to build and test with. Zaps with more than two steps need a paid Zapier plan.
Step by step
Set up the Zapier integration in six steps
- 1
Build a Parser Template
A Parser Template tells ParserBee what to look for. Build it once, and every document of that type is read the same way.
- In your ParserBee dashboard, click Templates in the sidebar, then Create Template.
- Upload one sample document and let the AI build the whole Parser Template for you, or start from a ready-made one in the template library (invoices, receipts, bank statements, purchase orders, CVs and more).
- Check the fields, rename anything you want, and save.
Test the Parser Template on a sample document on its page before you go near Zapier. A Parser Template that works in the dashboard works in a Zap.
- 2
Copy your API key
Go to Settings, open the API Keys tab and click the copy icon next to your key.
Your API key is a password. Anyone who has it can spend your page credits, so keep it out of emails, chat messages and shared documents. If you think it has been exposed, click Regenerate Key on the same screen. The old key stops working at once, and you need to reconnect ParserBee in Zapier with the new one.
- 3
Copy your Template ID
Zapier needs to know which Parser Template to use on each document.
Go to Templates and open the Parser Template you want. Near the top of the page, find Template ID and click the copy button beside it. The ID is a short string of letters and numbers. Keep it handy with your API key.
- 4
Connect ParserBee to Zapier
- In Zapier, click Create and start a new Zap.
- Choose your Trigger: the app that starts the automation. This is wherever your documents show up, for example a Google Drive folder, a OneDrive folder or a form submission.
- For the Action, search for ParserBee and choose Extract Data From Document.
- Zapier asks you to sign in to ParserBee. Paste your API key and click Connect.
The connection is saved to your Zapier account, so you do this only once. Every future Zap can reuse it.
- 5
Set up the action
The action has two fields. In Template ID, paste the ID from step 3: it decides which fields come back. In Document URL, click the field and pick the link that comes out of your trigger step, for example a direct link from your cloud drive or the file URL from a form submission.
The Document URL must be a direct link to the file itself. This trips people up more than anything else:
- It must open without a login. If someone who is not signed in to your account cannot open it, ParserBee cannot either.
- It must return the document, not a preview page. A “view in browser” link usually returns a web page with the document inside it, and ParserBee reads the page instead of the file.
- It should end with the file name, for example
.../invoice-2026-014.pdf. That is how ParserBee knows what kind of file it is.
Sources that work well: file upload fields in form tools (Typeform, Jotform, Gravity Forms, Tally), direct download links from cloud drives, links from your own systems sent through a webhook, and any file already on your website or CDN.
Documents arrive as email attachments? Add one step in the middle: have Zapier save the attachment to your cloud drive first, then give ParserBee the direct link. Email support@parserbee.com and we will help you wire it up.
Then click Test step. Zapier sends one real document through ParserBee and shows you exactly what comes back. The test uses page credits, the same as any other extraction.
- 6
Send the data where you need it
Add one more action to the Zap: the app where the data should land. Google Sheets, Airtable, Slack, your CRM, your accounting tool, or a webhook into your own system.
When you set up that step, every field ParserBee found appears in Zapier's field picker, ready to drop into the right column or box.
Click Publish and the Zap is live. From then on it runs on its own.
Set-up help from real people
Stuck, or short on time? We will set it up with you.
Send us one sample document and tell us where the data should go. Our team builds the Parser Template, connects Zapier and checks the first rows with you, end to end. Stuck halfway? Send a message and we pick it up from exactly where you are.
- We build or fine-tune the Parser Template for your documents
- We connect Zapier and test it with a real document
- We fix whatever is blocking you, at any step
Talk to the ParserBee team
Tell us about your documents and your tool. We reply with the next step, or set it up together with you.
Chat with our team →Email support@parserbee.comBuild your first Zap today
Create a free account, copy your API key and Template ID, and add the Extract Data From Document action. 25 free pages, no credit card.
Output
What ParserBee sends back after each document
| What comes back | What it means |
|---|---|
| Your fields | Everything your Parser Template asked for, one entry per field. If the Parser Template pulls repeating rows (invoice line items, for example), you get a list of records instead of a single set. |
| Request ID | The reference for this extraction. Quote it if you ever contact support. |
| Pages processed | How many pages were read in this document. |
| Credits charged | Page credits used by this document. |
| Credits remaining | What is left in your account afterwards. |
| Processing time | How long the extraction took, in milliseconds. |
Page credits
How page credits work with Zapier
The Zapier integration costs the same as everything else in ParserBee: one page credit per page, minimum one per document. A one-page invoice costs one credit. A ten-page contract costs ten.
Test runs cost credits
Every time you click Test step, a real document goes through ParserBee.
At zero, the Zap stops
Zapier shows the runs as failed and emails you. Upgrade your plan and the Zap picks up again by itself, with no reconnection.
See every extraction
Your balance is always in the dashboard sidebar, and Activity lists every extraction, from a Zap or anywhere else.
Troubleshooting
Fix the most common Zapier errors
These are the errors the ParserBee Zapier integration returns most often, what each one means and how to clear it.
| What you see in Zapier | What it means | How to fix it |
|---|---|---|
| Invalid API key | The key was mistyped, or it was regenerated after you connected. | Copy the key again from Settings, then reconnect the ParserBee account in Zapier. |
| Insufficient page credits | Your balance has run out. | Upgrade your plan, or wait for your next billing cycle. Nothing else needs changing. |
| No active subscription | The account is not on a trial or a paid plan. | Check the Billing page in your dashboard. |
| Template not found | The Template ID is wrong, or that Parser Template has been deleted. | Copy the ID again from the Parser Template's page. Watch for stray spaces at either end. |
| template_id is required | The Template ID field was left empty. | Fill it in. It is required on every run. |
| Either file or file_url is required | The Document URL field is empty, or the trigger step did not produce a link. | Open the trigger step's test data and check there really is a URL in the field you mapped. |
| Invalid file_url format | What arrived in the field was not a full web address. | The link must start with https://. A file name on its own will not work. |
| Failed to process document | ParserBee could not read the document. | Three usual causes: the link needs a login, the link returns a preview page instead of the file, or the PDF is password protected. Paste the link into a private browser window: if the file does not download, ParserBee cannot read it either. |
| The step times out | Very large documents can take longer than Zapier waits for a reply. | Split long PDFs, or run big files through Data Lab in your dashboard instead. |
| It runs, but fields come back empty | The document does not contain what the Parser Template asks for, or the field descriptions are too vague. | Open the Parser Template, make each description more specific, and test it again on the Parser Template page. |
Still stuck? Email support@parserbee.com with your Request ID. You find it in Activity in your dashboard and in the Zap's run history in Zapier, and it lets us look at exactly what happened on that run.
Good to know
Tips for a smooth set-up
Describe fields as you would to a colleague
“The final amount payable including tax” gets a better result than “total”. Be clear about dates, and say which format you want them in.
Test in the dashboard first
Run the Parser Template on a sample on its own page before you build the Zap. If it works there, it works in Zapier.
Watch for stray spaces
A space at either end of a pasted Template ID is the most common cause of Template not found.
Connect once
The ParserBee connection is saved in Zapier, so every new Zap can reuse it. You can save several ParserBee accounts and pick one per step.
One Parser Template per step
Each Extract Data From Document step uses one Parser Template. For several document types, use one Zap per type or Zapier's Paths.
Keep the Request ID
Every run returns one. Send it with any question and we can look at exactly that run.
FAQ
Zapier questions
Does the Zapier integration cost extra?
No. The ParserBee Zapier integration uses the same page credits as the rest of ParserBee: 1 per page. You may need a paid Zapier plan if your Zap has more than two steps, but that is Zapier's own pricing, not ours. See ParserBee pricing.
Which file types can ParserBee read?
PDF, PNG, JPG, WebP, HEIC (iPhone photos), DOC, PPT, PPTX, XLSX, CSV, TXT, RTF, ODT, HTML and EML. Scans and phone photos are fine. Word .docx files are not supported: save them as PDF first.
Can ParserBee start a Zap by itself?
Not yet. Today ParserBee is an action: something else starts the Zap and ParserBee does the reading. Triggers that fire when an extraction finishes are on the way. To send every extraction to a sheet or a base on its own, use the built-in Google Sheets or Airtable integration.
Can one Zap handle several document types?
Each Extract Data From Document step uses one Parser Template. If you handle several document types, build one Zap per type, or use Zapier's Paths to send each type to its own ParserBee step.
Can I use more than one ParserBee account in Zapier?
Yes. Zapier lets you save several connections and pick which one each step uses.
What happens to my documents?
When you send a link, ParserBee reads the document from that link and keeps only the extracted data in your Activity log, so you can check any result later. Documents are never used to train AI models, and everything is handled in line with GDPR. See our Privacy Policy for the detail.
Do I have to use Zapier at all?
No. Zapier is only one way in. To process a batch now and then, Data Lab in your dashboard needs no setup: upload a stack of files and export to Excel, CSV, PDF or Google Sheets. For a running sheet or base, the built-in Google Sheets and Airtable integrations need no Zap. Developers can use the REST API, and Make and n8n call it with their HTTP modules.
More integrations
Send your data somewhere else too
Put Zapier on autopilot
Invoices, receipts, purchase orders and more, read once and sent where your team works.