Extract Passport Data with Zapier and Cryvis

Passport KYC fails in Zapier when the Custom Request sends the wrong multipart shape. Cryvis expects two parts — first_page (biodata) and last_page (final page) — not a single file. This Zap takes two uploads, extracts biodata + MRZ, and writes Sheets or HubSpot.

Hub: Zapier + Cryvis. Multipart cheat sheet: Send multipart form data. Sibling KYC: Extract Aadhaar.

Architecture

Source (pick one)
  - Google Drive: two files in a pair folder / naming convention
  - Forms: biodata upload + final-page upload
        |
        v
Filter: both binaries present
        |
        v
Webhooks by Zapier: Custom Request
  POST https://api.cryvis.com/v1/documents/passport
  multipart: first_page + last_page
  Authorization: Bearer <API_KEY>
        |
        v
Filter: success is true
        |
        v
Destination
  Google Sheets row  OR  HubSpot Create/Update Contact

Prerequisites

• Cryvis API key with passport extraction — Passport API
• Zapier account
• Two clear page images/PDFs (biodata + final)
• Destination: Google Sheet or HubSpot with custom properties

Credits: 1 per image/page — a dual-image call typically costs two credits. See Credits.

Wrong vs right multipart

# Wrong — will not match the API contract
part: file = passport.jpg

# Right
part: first_page = biodata.jpg
part: last_page  = final.jpg

There is no file field on passport. Do not reuse the invoice/receipt multipart pattern.

Step 1: Source files

Option A — Forms with two file questions (biodata + final page). Copy: “Upload biodata and final page. Both required.”

Option B — Drive: two files named predictably (e.g. passport-front.jpg, passport-back.jpg) or two consecutive uploads your Zap can pair. If you only have one Drive trigger, use a Form for KYC intake — pairing two independent Drive events is fragile.

Add a Filter before Cryvis: both binaries must exist. Passport calls with only one part return a client error.

Step 2: Call Cryvis Passport API

Webhooks by Zapier → Custom Request

MIME: application/pdf, image/jpeg, image/png, image/webp.

Docs: extractPassport.

Step 3: Response

{
  "success": true,
  "data": {
    "full_name": "JOHN DOE",
    "given_name": "JOHN",
    "surname": "DOE",
    "date_of_birth": "1995-04-12",
    "nationality": "IND",
    "passport_number": "P1234567",
    "issue_date": "2020-04-12",
    "expiry_date": "2030-04-12",
    "issuing_country": "IND",
    "sex": "M",
    "mrz": {
      "line1": "P<INDDOE<<JOHN<<<<<<<<<<<<<<<<<<<<<<<<<<<<",
      "line2": "P1234567<3IND9504124M3004123<<<<<<<<<<<<<<<4",
      "check_digits_valid": true
    }
  },
  "meta": {}
}

Map:

Fields can be null on bad scans. Guard HubSpot updates so nulls do not wipe existing CRM data.

Step 4a: Google Sheets destination

Headers:

Full Name | Passport Number | DOB | Nationality | Issue | Expiry | Issuing Country | Sex | MRZ Valid | Source | Processed At

Create Spreadsheet Row from the paths above. Prefer storing mrz.check_digits_valid over raw MRZ lines in a shared Sheet.

Step 4b: HubSpot destination

Create custom properties once: passport_number, passport_nationality, passport_issue_date, passport_expiry_date, passport_issuing_country, passport_mrz_valid, kyc_status.

Create/Update Contact keyed by email from the Form:

Paths after success:

Path A: mrz.check_digits_valid is true → kyc_status = passport_extracted
Path B: false → kyc_status = passport_mrz_review (+ optional Slack)

Optional expiry Filter: only mark extracted when expiry_date is far enough in the future for your policy.

Errors and testing

Testing checklist

1. Two clear JPEGs → success: true, non-null passport_number.
2. Only biodata → expect failure; Filter should catch before HTTP when possible.
3. Swapped pages → degraded fields / MRZ — biodata must be first_page.
4. MRZ fail fixture → check_digits_valid: false → review Path.

Troubleshooting

Production notes

• Do not put raw MRZ lines on every CRM contact layout; store the boolean and keep lines in a restricted Sheet or vault if fraud review needs them.
• Swapping first_page and last_page is the most common silent quality bug.
• Plan volume against Credits and Pricing.

Related

• Send multipart form data
• Extract Aadhaar
• Passport API · extractPassport · Zapier hub · Sign up