Read Barcodes from PDF in Make
What this module does
PDF4me — Read Barcodes from PDF automatically detects and extracts barcode data from any PDF document in your Make scenario — scanned invoices, shipping labels, packing slips, or digitally generated documents. It returns an array of barcode text values that you can use immediately to route documents, look up records in a database, rename files, or trigger any downstream action. No manual scanning, no OCR configuration — point it at a PDF and the barcode data comes back ready to use.
Authenticating Your API Request
Every PDF4me module in Make requires a valid Connection. Create or select one that holds your PDF4me API key so the scenario can authenticate barcode extraction requests securely.
Important Facts You Should Not Miss
The Document / public file URL field accepts either a binary file buffer mapped from a prior module — such as a cloud storage download or email attachment — or a direct HTTPS URL pointing to the PDF. You do not need to download the file first if it is publicly accessible.
When you do not know which barcode type the document contains, tick Select All. The module scans for Code128, Code39, DataMatrix, PDF417, and QRCode in a single pass. If you know the format, selecting only that type speeds up processing — useful for high-volume document workflows.
Barcode Data returns every barcode found as a separate array entry. If you only need the first barcode, reference Barcode Data[1] directly. If a document may contain several barcodes — like a packing slip with one barcode per line item — add a Make Iterator after this module to process each value individually.

File set to Map passes the filename and PDF from any prior module. Select Barcode Type lets you target specific formats or scan all at once.
Parameters
Required: Connection, File Name, and Document / public file URL must all be provided. Select Barcode Type defaults to all formats if left at Select All.
| Parameter | Required | What it does | Example |
|---|---|---|---|
| Connection | Yes | PDF4me API connection. Click Add and paste your API key if connecting for the first time. | Your PDF4me connection |
| File Name | Yes | Source PDF filename including the .pdf extension. Map from the prior module's file name output. | invoice_scan.pdf |
| Document / public file URL | Yes | Binary PDF buffer from a prior module, or a publicly accessible HTTPS URL to the PDF. Scanned and digital PDFs both work. | 1. Data or https://example.com/doc.pdf |
| Select Barcode Type | Yes | Barcode formats to scan for: Select All, Code128, Code39, DataMatrix, PDF417, or QRCode. Select All scans every format in one pass. | Select All |
Quick Setup
- Add PDF4me → Read Barcodes from PDF to your Make scenario.
- Select Connection (or click Add to create one with your API key).
- Set File Name and Document / public file URL from the prior module — a cloud storage download, email attachment, or HTTP response.
- Under Select Barcode Type, tick Select All or choose the specific format your documents use.
- Click Save and run the scenario. The Barcode Data output contains an array of extracted text values — reference
Barcode Data[1]for the first result or add an Iterator to loop through all values.
Workflow Examples
Workflow ExamplesCommon Make scenario patterns using Read Barcodes from PDF.
- Dropbox Watch Folder triggers when a new scanned PDF arrives.
- Read Barcodes from PDF extracts the barcode text from the document.
- A Router checks Barcode Data[1] — if it starts with "INV-" it goes to the Invoices folder, "ORD-" to Orders, "RCP-" to Receipts.
- Each route uploads the file to the correct Google Drive destination folder.
- Email Watch triggers when a PDF invoice arrives as an attachment.
- Read Barcodes from PDF extracts the invoice number barcode.
- Google Drive upload uses Barcode Data[1] + ".pdf" as the filename — the file is stored under its invoice number automatically.
- A Slack message notifies the accounts team that a new invoice has been filed.
- A webhook fires when a shipping label PDF is generated.
- Read Barcodes from PDF extracts the tracking number barcode from the label.
- An HTTP module queries the shipping API with the tracking number to retrieve delivery status and customer details.
- A Gmail module sends the customer an automatic dispatch notification with the tracking number.