Zapier Document Extraction with Cryvis

Zapier moves files between apps. Cryvis turns those files into structured JSON. Put them together and you get a Zap that watches Drive, Gmail, or a form upload, posts the document to an API, and writes the fields into Sheets, Airtable, HubSpot, or Slack.

This hub covers how Cryvis fits in Zapier, which endpoint to call, how auth and credits work, and a full index of tutorials.

Prefer Make.com? See the Make.com + Cryvis hub. Prefer self-hosted workflows? See the n8n + Cryvis hub.

How Cryvis fits in a Zap

Cryvis is not a native Zapier app. You call it with an HTTP step that supports multipart/form-data — typically Webhooks by Zapier → Custom Request, or another action that can attach file binaries as form parts.

Typical pattern:

[Trigger: New File in Drive / Gmail Attachment / Form]
        |
        v
[Download / get file binary]
        |
        v
[Webhooks: Custom Request]
  POST https://api.cryvis.com/v1/documents/<type>
  Authorization: Bearer <API_KEY>
  Body: multipart/form-data
  Field: file = binary from previous step
        |
        v
[Filter: success is true]
        |
        v
[Destination: Sheets / Airtable / HubSpot / Slack]

Notes that save debugging time:

• Multipart field names depend on the endpoint: invoices/receipts/PAN use file; passport uses first_page + last_page; Aadhaar uses one or two parts named file; driver license needs file + country; Indian vehicle RC uses front and/or back.
• Accepted MIME types (typical): application/pdf, image/jpeg, image/png, image/webp.
• Response shape: { success, data: { ...fields }, meta }. Map from data.*, not the top-level wrapper.
• Credit cost: 1 credit per PDF page or image. See Credits.

Auth

1. Create an API key in the Cryvis console.
2. On the HTTP / Custom Request step, add a header:

Authorization: Bearer <API_KEY>

Store the key in a Zapier storage field or a secret your team controls. Do not paste live keys into shared Zap templates you publish publicly.

Endpoint cheat sheet

Base URL for all of the above: https://api.cryvis.com.

Invoice fields you will map most often: invoice_number, invoice_date, due_date, currency, seller, buyer, line_items[], subtotal, tax_total, total_amount, amount_due.

Credits

Every successful extraction consumes credits: 1 per PDF page or image. Multi-page PDFs cost one credit per page. Failed auth or bad MIME usually do not consume extraction credits — check Credits before you go live on a high-volume inbox.

Tutorial index

Invoice

• Extract invoice data into Google Sheets
• Invoice OCR to Airtable
• Automate invoice processing from Gmail

Receipts

• Extract receipt data with Zapier

KYC

• Automate KYC document checks
• Extract passport data
• Extract PAN card data
• Extract Aadhaar data
• Extract driver's license data

Vehicle

• Extract Indian vehicle RC

PDF / structured extraction

• Convert PDFs to JSON with a custom extractor

HTTP building blocks

• Send multipart/form-data from Zapier

Start here

If you only need invoice headers in a spreadsheet, begin with Extract invoice data into Google Sheets. For Gmail intake with Slack alerts, use Automate invoice processing. For the raw HTTP mechanics, jump to Send multipart/form-data.

Ready to extract: sign up, create a key, open the Invoice API, and wire the first Custom Request against extractInvoice.