Overview & Available Integrations

Ocriva integrates with third-party services through webhook-based event delivery. When documents are processed, batches complete, or templates change, Ocriva sends real-time HTTP notifications to your connected services — no polling, no manual exports, no glue code required.

Every integration in this section is built on the same underlying mechanism: a webhook endpoint registered in Ocriva that receives a JSON payload the moment an event fires. The difference between integrations is simply which URL you point that webhook at and how the receiving service interprets the payload.

How Integrations Work

When you connect Ocriva to an external service, the data flows in one direction — from Ocriva outward:

Document uploaded
      |
      v
AI processes & extracts
      |
      v
Event fired (e.g. document.processed)
      |
      v
Webhook delivers JSON payload
      |
      v
Third-party service acts
(send Slack message, trigger Zap, append Sheet row, etc.)

Payload Customization with {{variable}}

Ocriva uses a {{variable}} template system so you can shape exactly what gets sent to each integration. When configuring a webhook, you can reference any field from the event payload using double-brace syntax:

Document "{{payload.fileName}}" processed successfully.
Confidence: {{payload.confidence}}
Extracted by: {{payload.templateName}}

At delivery time, Ocriva substitutes each placeholder with the real value from the event. This lets you craft Slack messages, Discord embeds, or Zapier field mappings without writing any server-side code.

See the Webhooks Guide for full details on payload structure, signature verification, and retry behavior.

Available Integrations

Categories

Messaging — Slack, Discord

Messaging integrations deliver real-time team notifications when documents succeed or fail. They are the fastest way to keep a team informed without anyone needing to log into Ocriva.

• Post to a dedicated #ocr-results channel when high-confidence extractions land
• Alert #ops-alerts immediately when a document fails processing
• Mention specific users or roles for urgent documents

Automation — Zapier, Make, n8n

Automation platforms connect Ocriva to hundreds of downstream services without writing code. Once Ocriva fires an event, the automation platform receives it as a trigger and can route extracted data anywhere:

• Push invoice fields into an accounting system (Xero, QuickBooks)
• Create CRM records from extracted contact information (HubSpot, Salesforce)
• Store structured data in a database or data warehouse
• Chain multiple actions — notify Slack, write to Sheets, and open a Jira ticket all from one event

File Storage — Google Drive

The Google Drive integration is fundamentally different from other integrations — it's not an outbound webhook but a bidirectional connection:

• Pull: Fetch documents from a Google Drive Input Folder into Ocriva for automatic processing
• Push: Export results (JSON/CSV) back to a Google Drive Output Folder as soon as processing completes
• Configure Input/Output Folders per Template — invoices go to one folder, contracts to another
• Teams work in Google Drive as usual — just upload documents to Drive, Ocriva handles the rest
• Supports organization Shared Drives — manage permissions through standard Drive sharing

Spreadsheet — Google Sheets

Google Sheets integration logs extracted data directly into a spreadsheet row every time a document is processed. This is useful for teams that want a lightweight, human-readable audit trail or need to share results without setting up a database.

Mobile — LINE

The LINE integration is a first-class mobile workflow. Users scan a document with their phone, send it to a configured LINE bot, and receive the extracted result as a reply — all without opening a desktop browser. It is particularly popular in markets where LINE is the primary business communication tool.

Prerequisites

Before setting up any integration, confirm the following:

• An active Ocriva organization with available webhook quota (check Organization → Limits)
• A project to scope webhook events — integrations are always attached to a specific project
• Credentials for the target service (Slack workspace admin access, Discord server permissions, a Zapier or Make account, etc.)

Quick Start

The setup flow is the same regardless of which integration you choose:

1. Open the Integrations page in Ocriva (sidebar → Integrations).
2. Select the service you want to connect.
3. Follow the service-specific setup to obtain a webhook URL from that service (each guide below walks through this step).
4. Paste the webhook URL into Ocriva.
5. Choose which events to subscribe to (see Event Types below).
6. Optionally configure a secret for signature verification.
7. Click Test Connection — Ocriva sends a sample payload and confirms delivery.

Event Types for Integrations

The three events most commonly used with integrations are:

See Event Types & Payloads for the complete reference including template.updated, document.exported, and all payload field definitions.

What's Next

Pick the integration that matches your workflow:

• Slack Setup — post to channels with custom message formatting
• Discord Setup — send embeds to Discord channels
• Zapier Setup — trigger Zaps from any document event
• Make Setup — build Make scenarios with Ocriva as the trigger
• n8n Setup — connect to self-hosted or cloud n8n workflows
• Google Sheets Setup — append extracted data rows automatically
• LINE Integration — scan and receive results over LINE
• Webhooks Setup — build a fully custom integration against any HTTP endpoint