Integrations · Zapier

A dataroom that drives your tools.

Send a tracked document, open a dataroom, propagate every step to your CRM, your document store or your messaging — 8,000+ apps through Zapier, without writing code. Every event leaves signed and stays verifiable.

webhook delivery · dataroom → Zapier
POST hooks.zapier.com/hooks/catch/21819656/…
200 · received by Zapier
event record.appended · HMAC-signed
delivery succeeded · 1st attempt
body {
"id": "f7d3c8aa-6150-4fdc-…",
"type": "record.appended.…",
"data": { "dataroom_id": "…",
"chain_hash": "…" }
}
RIGA eventZapierCRMDMSSlackAirtable

Why Zapier

The RIGA API, without writing code.

No development required

One RIGA account and one Zapier account are enough. Your datarooms drive your tools without writing or maintaining integration code.

Your manual steps, automated

Each step of the workflow propagates to your systems of record, in real time.

Signed, logged delivery

Signed delivery, automatic retries, a delivery log in the console.

Use case · Tracked sends

Know who viewed your document, within the minute.

Send a tracked document from Zapier — a deal won in the CRM, a row added in Airtable — and receive every view and every download as an event: a Slack alert, a follow-up in the CRM, a row in your tracking sheet. Every view is a chain entry, dated and verifiable.

Example Zap

send.viewed Slack alert to the account owner
send.downloaded follow-up scheduled in the CRM
deal won tracked document sent
SlackHubSpotAirtableGmail

Use case · CRM

Sync your dataroom lifecycle into your CRM.

When a dataroom opens or a party joins the dataroom, create or update the matching deal and contact — in HubSpot, Salesforce, Pipedrive, Airtable or Notion. Your CRM record follows the transaction, with no re-keying.

Example Zap

record.appended deal updated
party joining contact created and linked
dataroom opened new deal

Every event carries the dataroom identifier and the chain hash — enough to find the exhibit from the CRM.

HubSpotSalesforcePipedriveAirtableNotion

Use case · Document store

Archive your sealed evidence files automatically.

When a dataroom closes, the dataroom.closed event triggers the chain export — the offline-verifiable evidence file — and files it into the right folder of your Google Drive, Dropbox, OneDrive or SharePoint. Your document store keeps the evidence, filed with the rest of the case.

Example Zap

resolution consented evidence file archived
dataroom closed chain export requested and archived
Google DriveDropboxOneDriveSharePoint

Use case · Notifications

Follow every step of the workflow, where your team works.

A question opened, a task completed, a resolution consented: each step notifies your team in Slack, Teams, Gmail or Outlook, in real time. The transaction thread lands directly in the channel.

Example Zap

question opened Slack message to the channel
task completed email to the team
consent signed Teams alert
SlackMicrosoft TeamsGmailOutlook

Use case · Start a workflow

Open a dataroom from the tools you already use.

Automation runs both ways. A new row in Airtable, a deal won in your CRM, a form received: Zapier opens the matching mediation or dataroom, creates the parties and sends the invitations — in a single call.

The dataroom starts with its context, roles and access in place. The rest of the workflow proceeds in the dataroom, where every step is written to the chain.

Action · a single call

Open a mediation
dataroom + two parties + invitations
Create a dataroom
AirtableHubSpotTypeformGmail

Catalog

The integration's triggers and actions.

Triggers · RIGA → Zapier

send.viewed · downloaded · created · revoked · expired
record.appended · corrected · retracted
dataroom.opened · closed
task.assigned · completed
participant.accepted
resolution.proposed · consent.signed
qa.opened
delegation.granted · revoked

Actions · Zapier → RIGA

Send Tracked Documenthosted link + viewing events
Append Recordcontent plus a pointer to your own object
Revoke Sendthe link goes out of service
Create Task
Open Mediationdataroom + parties + invitations
Create Dataroom

Searches

Find Dataroomby title
Find Sendby matter reference
Get Recordtype, hash, chain event

A record always answers a task: the Create Task action opens one when your automation has none. For advanced steps — inviting a party, exporting a closure — the full v1 API stays reachable from Zapier through an authenticated request.

Verifiable delivery

Every event is signed at emission and verifiable on receipt.

Every delivery carries an HMAC signature and an idempotency key. The body is the event's canonical envelope, transmitted as is — your Zap receives exactly what the chain recorded. Verify the signature: if one byte of the body changes in transit, it no longer matches.

HTTP 200 · received by Zapier · Webhook-Signature: t=…,v1=…

Get started

Your first Zap in three steps.

  1. 1Generate an API key in the developer console — test mode, free.
  2. 2Connect riga.solutions in Zapier with that key, then pick the trigger or action — event subscription happens automatically.
  3. 3Map the event fields into the app of your choice — CRM, document store, messaging.

Available today

The full catalog — send, record and workflow triggers; tracked-send, mediation and dataroom actions — works today through the developer console and the v1 API. The Zapier app is under review for the directory; until then, access is invite-only.

Beta — the API may change, no SLA. The records you emit are real, verifiable chain entries. The webhook delivery shown is a real delivery to a Zapier Catch Hook, accepted with HTTP 200.

Zapier, HubSpot, Salesforce, Pipedrive, Airtable, Notion, Google Drive, Dropbox, OneDrive, SharePoint, Slack, Microsoft Teams, Gmail, Outlook and Typeform are trademarks of their respective holders. VAL — Verifiable Authorization Lineage — is an open protocol (Apache-2.0).