PDF Vector Make integrationAutomate PDF Vector with Make.
Can Make read your PDFs and pass what it finds to your other apps? The PDF Vector Make integration gives you 12 modules for documents, invoices, ID papers and academic publications. This page links your account and walks you through a first scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What does the PDF Vector Make integration do?
It puts PDF Vector inside a Make scenario, the automation you build as a chain of modules. A module is one brick of that chain. PDF Vector brings 12 of them: 11 actions that work on one document at a time and 1 search. You never start a scenario from PDF Vector itself, because the app has no trigger.
Invoice data without retyping. A supplier invoice lands in another app, and Extract Structured an Invoice hands its content to the next module as organized data. If you only need one answer, such as the amount due, Ask an Invoice is the shorter route.
A quick check on ID papers. An onboarding team receives a scanned identity document. Parse an Identity Document or Ask an Identity Document reads it inside the scenario, so nobody has to open the file by hand.
A literature watch for research teams. Search Academic Publications returns the matching papers as bundles, one item per publication, and Fetch Publications by IDs pulls the ones you already know by identifier.
Two limits to keep in mind. PDF Vector cannot start a scenario, so the first module comes from another app or from Make's schedule. And the official Make doc for this app says it was generated by AI and may contain mistakes, so test each module before you rely on it. To budget your runs, read Make pricing. If you hesitate between the two tools, n8n vs Make sets out the criteria, and Make training covers the editor from zero.
How do you connect PDF Vector to Make?
- 01
Copy your API key
You need an active PDF Vector account and an API key. In your PDF Vector account settings, open the API keys section and copy the key shown on the page. Keep it at hand for the next step.
- 02
Add a PDF Vector module
In Make, add any PDF Vector module to your scenario and click Create a connection. A connection is your PDF Vector account linked to Make once. The Connection name field is optional; a clear name helps when you have several accounts.
- 03
Paste the key and save
Paste the API key you copied, or follow the instructions Make shows on screen, then confirm. Every other PDF Vector module in your scenarios can now reuse this connection without asking for the key again.
Your first scenario with PDF Vector
GoalWhen an invoice reaches one of your apps, Make sends it to PDF Vector and gets its content back as organized data.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where your invoices arrive, since PDF Vector has no trigger of its own.
- 02
Add Extract Structured an Invoice
Click the + on the right of that first module, search for PDF Vector and choose Extract Structured an Invoice. Link your account with Create a connection if you have not done it yet.
- 03
Map the invoice
Fill the fields the module asks for, and map the invoice from the first module instead of typing anything. Each bundle, one item passing from module to module, carries one invoice.
- 04
Test with Run once
Click Run once to execute the scenario one time. Then read the bundles each module received, to confirm PDF Vector returned what you expected.
- 05
Schedule and switch on
Set the schedule on the first module with the clock, every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest interval.
What the PDF Vector modules do
PDF Vector gives you 12 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Ask a Document
ActionIn the docs onlyYou get an answer to a question about a document, straight into your scenario, without opening the file. The Make doc gives no description, so the name is the only guide here: open the module to see which fields it expects.
Ask an Identity Document
ActionIn the docs onlyPick this one to get a single answer out of an ID paper, going by what its name promises. It is the identity counterpart of Ask a Document, aimed at passports and ID cards.
Ask an Invoice
ActionIn the docs onlyOne question, one invoice, one answer your next module can use: that is what the name of this action points to. Choose it over the Extract Structured version when you want a single value rather than the full breakdown.
Extract Structured a Document
ActionIn the docs onlyInstead of one answer, this action aims to hand back a document's content as organized data your next modules can map, going by its name. Reach for it when a plain question is not enough and you need several values at once.
Extract Structured an Identify Document
ActionIn the docs onlyGoing by its name, this action turns an ID paper into organized data, several values in one go. The spelling "Identify" is how Make displays it, so search for that exact word in the module list.
Extract Structured an Invoice
ActionIn the docs onlyYour invoices come out as organized data that the rest of the scenario can map, which is what the first scenario above uses. Judging by the two names, it gives a fuller result than Ask an Invoice, which aims at one value.
Fetch Publications by IDs
ActionIn the docs onlyWhen you already hold the identifiers of some papers, this action should bring those publications into your scenario, going by its name. It complements the search module: search finds, this one retrieves what you point it to.
Make an API Call
ActionIn the docs onlyAnything the other 11 modules do not cover, you can still reach: this module calls any endpoint of the PDF Vector API from your scenario, with the same connection. It is the fallback, not the first choice.
Parse a Document
ActionIn the docs onlyParse a Document should turn a document into content the next modules can read, judging by its name. Think of it as the first pass, before any question or extraction, when you simply want the text to travel on.
Parse an Identity Document
ActionIn the docs onlyA scanned passport or ID card becomes readable content inside Make with this action, if its name is taken at face value. Prefer it to the Ask variant when you want everything the card shows, not a single answer.
Parse an Invoice
ActionIn the docs onlyHere the invoice itself is read and passed on as content, the invoice sibling of Parse a Document by name. Take it when you want the text of the bill, and Extract Structured an Invoice when you want neat values.
Search Academic Publications
SearchIn the docs onlyJudging by its name, you describe a subject and get back the matching academic papers, each as its own bundle for the next module. As a search, it can return zero, one or several items, which is the key difference with the other PDF Vector modules.
Need help automating PDF Vector with Make?
A person reads every message.
