Skip to main content
PDF4me APIIntegrationsKnowledge BaseExtensionsAPI TesterBlog

AI-Shipping Label Parser for Zapier

What this action does

PDF4me AI-Shipping Label Parser lets you automatically extract shipping label data in Zapier — tracking numbers, carrier names, sender and recipient addresses, weight, dimensions, ship dates, and special handling instructions — from any PDF, PNG, or JPG label file. Connect it to any Zapier trigger (Gmail, Google Drive, Dropbox, Shopify, WooCommerce) and pipe the structured output directly into your order management system, warehouse platform, spreadsheet, or customer notification step. No code. No manual copy-paste. Just map your label file and every field comes back structured and ready to use.

Authenticating Your API Request​

Every PDF4me action in Zapier needs a valid Connection. Create or select a connection that holds your PDF4me API key so your Zap can call the AI extraction securely.

Get your API Key

Important Facts You Should Not Miss​

Map real binary file content

File must be actual binary data from a prior step — not a URL or filename string. Map it from the file-data output of your trigger (Gmail attachment, Google Drive file content, Dropbox). Passing a URL causes a failed extraction.

File Name must include the extension

The File Name field must end with .pdf, .png, or .jpg. PDF4me uses the extension for format detection. A name without an extension returns empty results. Example: Labels-199287-1.pdf.

Gate with confidence scores

Every field comes with a 0–1 confidence score. Add a Zapier Filter after the parser: continue only when confidence.trackingNumber > 0.85. Route low-confidence records to a review sheet instead of writing suspect data to your OMS.

Configure the Action in Zapier​

Open the Configure tab of the PDF4me AI-Shipping Label Parser step. Map File from the binary output of the previous step (shown as "Exists but not shown" in Zapier's UI — that is normal for file objects). Then build File Name by combining the File Name token and the File Ext token from your trigger so the result includes the extension (e.g. Labels-199287-1.pdf).

Zapier PDF4me AI-Shipping Label Parser Configure tab — File field set to step 2 binary file output showing 'Exists but not shown', File Name field assembled from File Name token (Labels-199287-1) and File Ext token (.pdf)

The Configure tab: File is mapped from step 2 (the binary label file — Zapier shows "Exists but not shown" for file objects, which is expected). File Name is assembled from two tokens — File Name and File Ext — producing Labels-199287-1.pdf. Use Refresh fields if step 2 was recently renamed and sample data is out of sync.

Key Features​

  • AI-powered extraction — reads printed and thermally printed labels; handles low-resolution scans, digital PDFs, and multiple label orientations
  • Full address parsing — sender and recipient split into individual fields: name, company, street, city, state, postal code, country
  • Carrier auto-detection — UPS, FedEx, DHL, USPS, Royal Mail, Australia Post, Canada Post, and regional carriers identified automatically
  • Tracking & barcode — primary tracking number, secondary barcodes, and carrier reference IDs returned as separate fields
  • Weight and dimensions — declared weight with unit (kg / lb) and package dimensions with unit (cm / in)
  • Special handling instructions — Fragile, Signature Required, Leave Safe, Do Not Bend captured as structured text
  • Per-field confidence scores — use to branch Zap logic, flag low-quality records, and protect downstream systems

Parameters​

Required: Connection, File, and File Name. All three must be configured before saving the action step.

ParameterRequiredWhat it doesExample value
ConnectionYesYour PDF4me API connection. Create one via "Add a new connection" and paste your API key from dev.pdf4me.com.My PDF4me connection
FileYesBinary content of the shipping label. Map the file data output (not a URL) from your trigger or a file-download step.1. Attachment (File Content)
File NameYesFile name including extension (.pdf, .png, .jpg). Used for format detection and AI optimization. Must include extension.Labels-199287-1.pdf
Custom Field KeysNoOptional list of extra field keys for the AI to extract — carrier-specific codes, routing zones, or hazmat classes not covered by the default output.["routingCode","hazmatClass"]

How to Extract Shipping Label Data in Zapier​

Follow these steps to set up the AI-Shipping Label Parser in any Zap. The whole setup takes under 5 minutes.

1
Add a PDF4me action step

In Zapier, click the + button to add a new Action. In the app search box, type PDF4me and select it. From the action list, choose AI-Shipping Label Parser.

2
Connect your PDF4me account

Click Sign in to PDF4me. A connection dialog opens — paste your PDF4me API key (get it free at dev.pdf4me.com/dashboard/#/api-keys/). Click Yes, Continue to save.

3
Map the File field to binary label data

Under File, click the + icon to map from a previous step. Select the file-data output — not a URL. From a Gmail trigger this is "Attachment"; from Google Drive it is "File Content"; from Dropbox it is "File Binary". The field must contain actual bytes, not a link.

4
Set the File Name with extension

Under File Name, map the filename from your trigger. Confirm it ends with .pdf, .png, or .jpg — for example Labels-199287-1.pdf. If your trigger returns the name without an extension, use Zapier Formatter (Text → Append) to add it before this step.

5
Add Custom Field Keys (optional)

If your carrier prints fields not covered by the default output — routing codes, zone identifiers, hazmat classes — enter them as a list in Custom Field Keys. Each key you add is returned as an extra field in the response.

6
Test the action

Click Continue then Test action. PDF4me processes the sample label and returns all extracted fields. Check that trackingNumber, carrierName, recipientAddress, and weight are populated correctly.

7
Add a confidence score filter

After the parser, add a Zapier Filter step. Set it to continue only when the confidence value for your most critical field (e.g. trackingNumber) is greater than 0.85. Route failed records to a review sheet or Slack alert.

8
Map output to downstream steps

Use the extracted fields — tracking number, addresses, carrier, weight, estimated delivery date — in subsequent Zapier steps to update Shopify orders, write to Google Sheets, send customer SMS/email, or post a warehouse notification in Slack.

What You Get Back​

Tip: After running Test action in Zapier, open the output panel to see the exact field names returned for your specific label. Field availability depends on what is printed on the label — fields not present on the label are returned as null or omitted. The table below shows the standard output set.

FieldTypeDescription
trackingNumberStringPrimary tracking number extracted from the label barcode or printed text
carrierNameStringCarrier identified from the label (e.g. UPS, FedEx, DHL, USPS, Royal Mail)
serviceTypeStringService level printed on the label (e.g. Ground, Express, Priority Mail)
senderNameStringSender name or company as printed in the From/Sender section
senderAddressStringSender street address
senderCityStringSender city
senderStateStringSender state, province, or region
senderPostalCodeStringSender postal code or ZIP
senderCountryStringSender country
recipientNameStringRecipient name or company as printed in the To/Recipient section
recipientAddressStringRecipient street address
recipientCityStringRecipient city
recipientStateStringRecipient state, province, or region
recipientPostalCodeStringRecipient postal code or ZIP
recipientCountryStringRecipient country
weightStringDeclared weight as printed on the label (value and unit may be combined, e.g. "2.3 lb")
shipDateStringShip date as printed on the label
referenceNumberStringReference number, order ID, or PO number printed on the label (if present)
confidenceObjectPer-field confidence scores (0–1). Confirmed across all PDF4me AI parsers. Use in a Filter step to gate data quality.
jobIdStringUnique identifier for this AI processing job — use for tracking and support
jobIdExtStringExternal job reference (null if not applicable)
successBooleantrue when extraction completed without errors
messageStringResult message from the API — describes success or the specific error

Workflow Examples​

Workflow ExamplesReal-world Zapier patterns built around the AI-Shipping Label Parser.
E-commerce: Email → Parse → Update Order
  1. Gmail / Outlook trigger — new email with shipping label attachment.
  2. AI-Shipping Label Parser — extract tracking number, recipient, carrier, ETA.
  3. Filter — continue only when success = true.
  4. Shopify / WooCommerce — update order with tracking number and carrier.
  5. Gmail / Twilio — send customer a branded shipping confirmation with tracking link.
Warehouse: Scanned label → Parse → Log
  1. Google Drive trigger — new scanned label PDF in receiving folder.
  2. AI-Shipping Label Parser — extract sender, tracking number, weight, dimensions.
  3. Paths — route by carrier or destination for different handling rules.
  4. Google Sheets / Airtable — append full shipment record to receiving log.
  5. Slack — notify warehouse team with parcel summary and special instructions.
Returns: Return label → RMA → Refund
  1. Dropbox / OneDrive trigger — return label uploaded by customer.
  2. AI-Shipping Label Parser — extract sender (returning customer) and reference number.
  3. Order lookup — match reference number to original order in Shopify or OMS.
  4. Create RMA record — populate return with all extracted fields pre-filled.
  5. Stripe / PayPal — trigger refund; send customer confirmation email.

Frequently Asked Questions​

What data does the AI-Shipping Label Parser extract from a shipping label?+
It extracts tracking number, carrier name, service type, full sender and recipient addresses (name, street, city, state, postal code, country), declared weight, package dimensions, package type, ship date, estimated delivery date, reference/order number, and special handling instructions. Every field is returned individually so you can map each one into downstream Zapier steps without any text parsing.
Which shipping carriers are supported?+
All major carriers are detected automatically: UPS, FedEx, DHL, USPS, Royal Mail, Australia Post, Canada Post, Deutsche Post, and most regional carriers. You do not specify the carrier — the AI reads the label and identifies it. For carrier-specific fields not in the standard output, use the Custom Field Keys parameter.
Why do I need to map file content instead of a file URL?+
The File field expects raw binary data — the actual bytes of the PDF or image — not a download URL. In Zapier, this is the "Attachment" output from a Gmail trigger or the "File Content" output from a Google Drive download step. Mapping a URL string causes the action to fail. If your trigger only provides a URL, add a Download File step (e.g., HTTP by Zapier) before the parser to convert the URL to binary content.
How do I use confidence scores to prevent bad extractions from reaching my OMS?+
After the parser action, add a Zapier Filter step and check: "Only continue if — Confidence trackingNumber — Greater than — 0.85". Records below the threshold are stopped here. To capture them for review instead of dropping them, use a Paths step: one path handles high-confidence records (write to OMS), the other handles low-confidence records (write to a review sheet or Slack alert).
Can I extract custom fields that my carrier prints on the label?+
Yes. Use the Custom Field Keys parameter to pass a list of field names you want the AI to look for — for example ["routingCode", "sortFacility", "hazmatClass"]. Each key is returned as an additional field in the response alongside the standard output. This is useful for carrier-specific barcodes, zone IDs, or any label fields not in the default field set.

Get Help​

PDF4me on ZapierAPI Keys