Make.com Document Extraction with Cryvis

Make.com moves files between apps. Cryvis turns those files into structured JSON. Put them together and you get a scenario that watches a folder or inbox, posts the document to an API, and writes the fields wherever your process already lives — Sheets, Airtable, Notion, HubSpot, Slack.

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

How Cryvis fits in a Make scenario

Cryvis is not a native Make app. You call it with the HTTP — Make a Request module using multipart/form-data.

Typical pattern:

[Trigger: Watch Files / Emails]
        |
        v
[Download / Get Attachment]  --> binary file
        |
        v
[HTTP: Make a Request]
  POST https://api.cryvis.com/v1/documents/<type>
  Authorization: Bearer <API_KEY>
  Body type: multipart/form-data
  Field: file = binary from previous module
        |
        v
[JSON: Parse JSON]  (if you prefer mapped fields over raw Body)
        |
        v
[Destination: Sheets / Airtable / Notion / Slack / HubSpot]

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 dashboard.
2. In Make, add a header on the HTTP module:

Authorization: Bearer <API_KEY>

Store the key in a Make connection or scenario variable. Do not hardcode it in shared scenario blueprints you export publicly.

Endpoint cheat sheet

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

Invoice response 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 for the exact rules before you go live on a high-volume inbox.

Tutorial index

Invoice

• Extract invoice data into Google Sheets
• Automate invoice processing from Gmail to Airtable
• Extract invoice data from Dropbox PDFs to Notion
• Extract invoice line items (one row per item)
• Automate accounts payable with Router + Slack
• Extract vendor details into HubSpot

Receipts

• Extract receipt data with Make.com
• Automate expense tracking
• Extract receipt data from images
• Convert receipts to JSON
• Employee expense workflow
• Receipt to Google Sheets

KYC

• Automate KYC document checks
• No-code KYC workflow
• Extract passport data
• Extract PAN card data
• Extract Aadhaar data
• Extract driver's license data
• Identity document processing

Vehicle

• Extract Indian vehicle RC
• Automate vehicle document processing
• Extract vehicle registration data
• Vehicle onboarding workflow

PDF / structured extraction

• Extract PDF data
• Convert PDFs to JSON
• Extract structured data from documents
• Build a custom document extractor
• Extract specific fields from PDFs

HTTP building blocks

• Send a PDF to an OCR API
• Upload a file to an API
• Send multipart/form-data
• Add Bearer authentication
• Parse API JSON responses
• Map API JSON fields
• Handle API errors
• Connect a REST API

Start here

If you only need invoice headers in a spreadsheet, begin with Extract invoice data into Google Sheets. For AP triage with amount thresholds, use Automate accounts payable. For the raw HTTP mechanics, jump to Send multipart/form-data and Add Bearer authentication.

Ready to extract: create a key, open the Invoice API, and wire the first HTTP module against extractInvoice.