Make (Integromat) Integration

Build visual automation scenarios that connect Ocriva to 1,000+ apps the moment a document is processed. Make's drag-and-drop scenario builder lets you route extracted data to accounting software, databases, spreadsheets, and more — without writing code.

Prerequisites

• A Make account (free plan is sufficient to get started)
• An Ocriva organization with available webhook quota

How It Works

Ocriva sends a raw JSON payload to Make's Custom Webhook module each time a subscribed event fires (e.g., document.processed). Make automatically parses the incoming JSON and exposes every field as a mappable variable in the rest of your scenario — no manual JSON parsing required.

For full details on the Make Webhooks module, see the Make Webhooks documentation.

Step 1: Create a Custom Webhook in Make

1. Log in to Make and open the Scenarios page
2. Click Create a new scenario
3. Click the + icon to add the first module, then search for Webhooks
4. Select Custom webhook from the module list
5. Click Add to create a new webhook configuration
6. Give the webhook a descriptive name (e.g., Ocriva - document.processed)
7. Copy the generated webhook URL — it will be in the format:

https://hook.make.com/...

8. Click OK — Make immediately begins listening on that URL

Step 2: Configure in Ocriva

1. Navigate to the Integrations page in the Ocriva dashboard
2. Find the Make template card and click it
3. Paste the webhook URL copied from Make into the URL field
4. Select the events you want to receive (default: document.processed)
5. Leave the payload template empty — Make receives the raw JSON and parses it automatically
6. Click Create Endpoint

The endpoint will be active immediately.

Step 3: Determine Data Structure

Make requires one sample payload to learn the shape of the incoming data before you can map fields to subsequent modules.

1. In Ocriva, open the endpoint you just created and click Test
2. Ocriva sends a sample document.processed payload to your Make webhook URL
3. Switch back to Make — the Custom Webhook module will show "Successfully determined"
4. Click OK to confirm the detected structure
5. The extracted fields (e.g., fileName, status, extractedData) are now available as mappable variables throughout your scenario

Example Scenarios

Invoice → Accounting (QuickBooks / Xero)

Route extracted invoice data directly into your accounting software:

1. Trigger: Custom Webhook (Ocriva document.processed)
2. Filter: Continue only if status equals success
3. Action: QuickBooks Online → Create Invoice (map extractedData.vendor, extractedData.totalAmount, extractedData.invoiceDate)

Receipt → Expense Report

Automatically create expense entries from receipt extraction:

1. Trigger: Custom Webhook (Ocriva document.processed)
2. Action: Google Sheets → Add Row (map fileName, extractedData.amount, extractedData.merchant, timestamp)

Document → Database

Save every extracted document to a structured database:

1. Trigger: Custom Webhook (Ocriva document.processed)
2. Action: MySQL / PostgreSQL / Airtable → Insert Record

Example field mapping for a database module:

Available Event Data

Make receives the same payload structure as all Ocriva webhooks. For the full list of fields available in extractedData and other event properties, see the Webhook Events reference.

Tips

• Use Make's Router module to split a single webhook into multiple branches — for example, one branch for invoices and another for receipts — based on a field in extractedData
• Use Make's JSON module (Parse JSON operation) if you need to access nested properties inside extractedData that Make did not auto-detect during structure determination
• Make's free plan includes 1,000 operations per month; each module execution in a scenario counts as one operation

Troubleshooting