Zapier Document Extraction with Cryvis
Wire Cryvis OCR APIs into Zapier with multipart HTTP, Bearer auth, and Zaps for invoices, receipts, KYC, and vehicle docs.
Read postPractical walkthroughs for document extraction, OCR APIs, and getting structured data out of PDFs and images.
Tutorials for connecting Zapier to Cryvis document extraction APIs. Start with the Zapier hub.
Wire Cryvis OCR APIs into Zapier with multipart HTTP, Bearer auth, and Zaps for invoices, receipts, KYC, and vehicle docs.
Read postBuild a Zap: Google Drive New File → Cryvis Invoice OCR → Google Sheets. Map invoice_number, dates, seller, and totals.
Read postDrive New File → Cryvis Invoice API → Airtable Create Record. Field types, bases, and status for AP intake.
Read postGmail New Attachment → Cryvis Invoice API → Google Sheets row plus Slack alert. Optional Paths for amount thresholds.
Read postCryvis multipart field names for Zapier Custom Request: file, passport first_page/last_page, RC front/back, driver-license country, and custom extractors.
Read postGoogle Drive New File → Cryvis Receipt API → Google Sheets. Map merchant, date, total, currency, and payment method.
Read postTwo-file passport upload (first_page + last_page) to Cryvis, then map biodata and MRZ into Google Sheets or HubSpot.
Read postUpload Aadhaar (1–2 multipart file parts) to Cryvis, write Google Sheets rows, and handle is_masked PII safely.
Read postWatch an India-KYC Drive folder, call Cryvis POST /v1/documents/pan with multipart file via Custom Request, and append PAN number, name, and holder type to Google Sheets.
Read postWatch Dropbox license scans, call Cryvis POST /v1/documents/driver-license with required ISO alpha-3 country via Custom Request, and sync fields into Notion.
Read postBuild a Zap that routes form or Drive KYC uploads by document type to Cryvis Passport, PAN, and Aadhaar APIs via Paths, then writes contact fields and KYC status to HubSpot.
Read postTurn non-standard PDFs into JSON in Zapier: create a Cryvis custom extractor in Console, POST multipart file to /v1/custom-extractors/:slug, map data into Google Sheets or a webhook.
Read postWatch Google Drive for RC front/back scans, call Cryvis POST /v1/documents/indian-vehicle-rc with multipart front and/or back via Custom Request, and append registration and chassis fields to a fleet Google Sheet.
Read postWorkflows that call Cryvis OCR and extraction APIs from n8n. Start with the n8n hub.
Call Cryvis OCR APIs from n8n with HTTP Request multipart, $binary files, Bearer auth, and workflows for invoices, KYC, and document ETL.
Read postn8n workflow: Google Drive → HTTP Request Cryvis Invoice API → IF success → Google Sheets. Map invoice_number, seller, totals.
Read postn8n strength vs spreadsheet zaps: Drive → Cryvis Invoice API → IF success → Postgres/MySQL INSERT with typed columns.
Read postn8n: Gmail trigger → IF MIME → Cryvis Invoice HTTP Request → Google Sheets + Slack. AP intake with success and error branches.
Read postConfigure n8n HTTP Request for Cryvis multipart OCR: Bearer auth, Form-Data file fields, $binary.data, and endpoint field variants.
Read postn8n workflow: Google Drive → HTTP Request POST /v1/documents/receipt → IF success → Google Sheets with merchant, totals, payment.
Read postn8n KYC flow: two binary properties → HTTP Request Form-Data first_page + last_page → IF success / MRZ → HubSpot or Sheets.
Read postn8n: Gmail attachments → Cryvis POST /v1/documents/aadhaar with one or two file parts → IF is_masked → Google Sheets with PII controls.
Read postWatch an India-KYC Drive folder, call Cryvis POST /v1/documents/pan with multipart $binary file, and append PAN number, name, and holder type to Google Sheets.
Read postWatch Dropbox license scans, call Cryvis POST /v1/documents/driver-license with required ISO alpha-3 country, and sync fields into Notion.
Read postBuild an n8n KYC workflow that routes webhook or form uploads to Cryvis Passport, PAN, and Aadhaar APIs via Switch, then writes contact fields and KYC status to HubSpot.
Read postTurn non-standard PDFs into JSON in n8n: create a Cryvis custom extractor, POST multipart $binary file, map data with Set/Code into Google Sheets or a webhook.
Read postWatch Google Drive for RC front/back scans, call Cryvis POST /v1/documents/indian-vehicle-rc with multipart front/back binaries, and append registration and chassis fields to a fleet Google Sheet.
Read postTutorials for connecting Make.com to Cryvis document extraction APIs. Start with the Make.com hub.
Wire Cryvis document APIs into Make.com with HTTP multipart, Bearer auth, and ready scenarios for invoices, receipts, KYC, and vehicle docs.
Read postBuild a Make.com scenario: Drive Watch Files → Cryvis Invoice API → Google Sheets. Map invoice_number, dates, seller, and totals.
Read postMake.com scenario: Gmail Watch Emails → Get Attachment → Cryvis Invoice API → Airtable Create Record for AP intake and status tracking.
Read postMake.com: Dropbox Watch Files → Download → Cryvis Invoice API → Notion Create Database Item. Map seller, buyer, dates, and totals.
Read postDrive → Cryvis Invoice API → Iterator on line_items → one Sheets row per item. Includes Array Aggregator notes for header+lines.
Read postGmail → Cryvis Invoice API → Router on amount_due → Slack alert for high-value invoices and Google Sheets for the AP log.
Read postMake.com: Drive → Cryvis Invoice API → HubSpot Create/Update Company from seller.name, tax_id, and related invoice fields.
Read postBuild a Make.com scenario that watches Google Drive for receipts, calls the Cryvis Receipt API, and writes merchant and total into Google Sheets.
Read postParse Gmail receipt attachments with the Cryvis Receipt API and log expenses into Airtable — merchant, date, tax, and total without manual entry.
Read postAccept JPEG and PNG receipts via Make.com webhooks or Google Forms, extract fields with Cryvis, and append merchant and totals to Google Sheets.
Read postWire Make.com HTTP modules to the Cryvis Receipt API: multipart uploads, single-file envelopes, and results[] batch responses mapped to downstream apps.
Read postRoute Google Forms receipt uploads through Cryvis extraction, Slack approval, and Google Sheets — write ledger rows only when managers approve.
Read postMap Cryvis receipt fields into a production Google Sheets ledger — column layout, receipt_number+date dedupe, and Make Data Store idempotency.
Read postBuild a Make.com KYC scenario that routes Typeform multi-file uploads to Cryvis Passport, PAN, and Aadhaar APIs, then writes contact fields and KYC status to HubSpot.
Read postBuild a Make.com KYC pipeline from a custom webhook through sequential Cryvis Passport, PAN, and Aadhaar checks into an Airtable applicant record.
Read postTypeform passport uploads to Cryvis POST /v1/documents/passport with first_page and last_page, then map biodata and MRZ fields into HubSpot.
Read postWatch an India-KYC Drive folder, call Cryvis POST /v1/documents/pan with multipart file, and append PAN number, name, and holder type to Google Sheets.
Read postParse Aadhaar attachments from Gmail with Cryvis POST /v1/documents/aadhaar, write Airtable rows, and handle is_masked PII safely.
Read postWatch Dropbox license scans, call Cryvis POST /v1/documents/driver-license with required ISO alpha-3 country, and sync fields into Notion.
Read postClassify KYC scans from an intake folder by MIME and filename, route to Cryvis Passport, PAN, Aadhaar, or Driver License APIs, and write results to your CRM.
Read postWatch Google Drive for RC front/back scans, call Cryvis POST /v1/documents/indian-vehicle-rc, and append registration and chassis fields to a fleet Google Sheet.
Read postParse Indian Vehicle RC attachments from email with Cryvis, store fleet records in Airtable, and flag insurance_valid_upto renewals.
Read postAccept Indian RC uploads from a form, extract chassis and engine numbers with Cryvis indian-vehicle-rc, and sync a Notion vehicle database.
Read postAccept vehicle onboarding webhooks, extract Indian RC data with Cryvis, create HubSpot deals, and use Error Handlers when documents are incomplete.
Read postChoose the right Cryvis endpoint for PDFs in Make.com—built-in invoice/receipt vs custom extractors—with a Drive→Invoice sample scenario.
Read postTurn non-standard PDFs into JSON in Make.com: create a Cryvis custom extractor, POST multipart file, map data into Google Sheets.
Read postPattern guide for Make.com × Cryvis: sources, document endpoints, and destinations—with ASCII workflows for finance, KYC, and custom PDFs.
Read postCreate a Cryvis custom extractor schema in Console, then call POST /v1/custom-extractors/:slug from Make.com HTTP with multipart file.
Read postDesign Cryvis custom extractor schemas for only the PDF fields you need, then map those keys in Make.com without pulling unused JSON.
Read postUse Make.com HTTP Make a Request to POST a PDF to Cryvis Invoice API—multipart file, Bearer auth, and JSON mapping. No generic OCR URL.
Read postMap Google Drive or Gmail binary attachments into Cryvis multipart uploads in Make.com—Buffer mapping, filenames, and MIME checks.
Read postCryvis multipart field names for Make.com HTTP: file, passport first_page/last_page, RC front/back, driver-license country, and custom extractors.
Read postSet Authorization Bearer headers for Cryvis in Make.com HTTP modules, reuse connections, and rotate API keys without rewriting scenarios.
Read postMap Cryvis success/data/meta envelopes in Make.com, and handle receipt batch results[] with file_name, data, and meta per file.
Read postMap nested Cryvis JSON in Make.com—seller.name, line_items arrays, nullables, and ifempty—without flattening by hand.
Read postConfigure Make.com Error Handlers for Cryvis HTTP calls—retries, 401/402/422 codes, and soft validation warnings in meta.
Read postEnd-to-end Make.com pattern for Cryvis REST: Bearer auth, multipart upload, parse JSON, map fields, and error handling on real document endpoints.
Read post