Integration guide · no code required

Connect DRIVUNO to Zapier

Get a Slack alert (or an Airtable row, a Jira ticket, an SMS…) every time something happens in DRIVUNO. About 10 minutes, no developer needed, and you can cut the connection at any time in one click.

No Zapier app to install No review or waiting Works on every plan with API access Revocable in one click

What actually happens

DRIVUNO sends a small notification (a “webhook”) to Zapier whenever an event occurs — a file was uploaded, a share was created, a teammate joined. Zapier catches it and runs whatever you want next, in any of its 7,000+ apps.

DRIVUNO

a file is uploaded

Webhook

signed event (metadata only)

Zapier

catches the event

Slack, Sheets…

your action runs

Your files stay unreadable

The notification contains identifiers, sizes and timestamps — never the file itself, never its name, never a message body. Zapier is told “a 10 MB file arrived in folder 6b21…”, nothing more. DRIVUNO holds no key that could reveal the content, so neither can any integration.

The 5-minute path (recommended)

1

Create your DRIVUNO API key

2 min
Open API & Webhooks in the app sidebar. Type a name you will recognise later (for example Zapier – Slack alerts), tick the scopes below, then press Create key.
files:readfolders:readevents:readwebhooks:write

Copy it immediately

The secret (dvk_live_…) is displayed once and never again — we only store a fingerprint of it. Paste it into your password manager before leaving the page. Lost it? Just revoke it and create another; it takes five seconds.
2

Create a Zap and copy its catch URL

1 min
In Zapier: Create → Zaps → Trigger, search Webhooks by Zapier, pick the event Catch Raw Hook, then Continue. Zapier shows a URL like the one below — copy it.
https://hooks.zapier.com/hooks/catch/123456/abcdef/

Good to know

“Catch Raw Hook” keeps the request exactly as sent, which is what the optional signature check in step 6 needs. If you never plan to verify signatures, plain “Catch Hook” also works and is slightly easier to read.
3

Paste that URL back into DRIVUNO

1 min
Back in API & Webhooks → Webhook endpoints, paste the URL, tick the events you care about, and press Register endpoint. That's the whole connection — no OAuth, no password shared with anyone.
file.uploadeda new file lands in your vault
file.trasheda file is moved to trash
file.shareda share link or team share is created
folder.createda new folder appears
member.addedsomeone joins a team or room
room.messagea message is posted in Rooms

Prefer doing it by command line?

Anything the interface does is also one API call:
curl -X POST https://drivuno.com/api/public/v1/subscriptions \
  -H "Authorization: Bearer dvk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "target_url": "https://hooks.zapier.com/hooks/catch/123456/abcdef",
    "event": "file.uploaded"
  }'
4

Send a test so Zapier learns the fields

30 sec
Press the small paper-plane button next to your endpoint in DRIVUNO (or simply upload any file). Then click Test trigger in Zapier — it will show the payload it received:

What Zapier receives

{
  "id": "5f2c...",
  "event": "file.uploaded",
  "created_at": "2026-08-02T14:00:00.000Z",
  "data": {
    "file_id": "0f0c...",
    "folder_id": "6b21...",
    "ciphertext_size": 10485760,
    "version": 1,
    "encrypted": true
  }
}

Good to know

If Zapier says “We couldn't find a request”, make sure the Zap is open on the “Test trigger” screen, then press the test button in DRIVUNO again. Deliveries are also logged under Recent deliveries in DRIVUNO, with the HTTP status Zapier returned — that tells you instantly which side is at fault.
5

Choose what should happen

2 min
Add an action step: Slack → Send Channel Message, Google Sheets → Create Row, Jira → Create Issue… Then drag the fields from step 4 into the message. A message that works well:

Slack message template

📁 New file in DRIVUNO
Folder: {{data__folder_id}}
Size: {{data__ciphertext_size}} bytes
When: {{created_at}}
Turn the Zap on. You're live.
6

Optional — verify the signature (production)

3 min
Every delivery carries a header proving it really came from DRIVUNO and was not replayed. Add a Code by Zapier (JavaScript) step right after the trigger:
const crypto = require("crypto");
const secret = "whsec_...";              // copy from API & Webhooks
const raw = inputData.rawBody;           // Catch Raw Hook body
const [tPart, v1Part] = inputData.signature.split(",");
const t = tPart.slice(2);
const expected = crypto.createHmac("sha256", secret)
  .update(t + "." + raw).digest("hex");

if (expected !== v1Part.slice(3) || Math.abs(Date.now()/1000 - Number(t)) > 300) {
  throw new Error("Invalid or stale DRIVUNO signature");
}
output = [JSON.parse(raw)];

Good to know

Map rawBody to the raw body and signature to the X-Drivuno-Signature header in the step's input fields. Skipping this step is fine for internal notifications; do it when a Zap performs a real action (payments, tickets, provisioning).

Ready-made recipes

New file → Slack alert

file.uploadedSlack message

The classic. Your team sees production drops land in real time, without anyone exposing a file name.

New file → Airtable / Sheets log

file.uploadedCreate row

An auditable inventory: file id, size, version, timestamp. Useful for billing clients per delivery.

Share created → compliance ticket

file.sharedJira / Linear issue

Every outbound share gets reviewed by a human. Auditors love this one.

Member added → onboarding

member.addedHR / IT workflow

Provision the mailbox, the laptop and the badge the moment someone joins a team space.

Rooms message → paging

room.messagePagerDuty / SMS

On-call routing. The message body stays encrypted — only the fact that one was posted travels.

Daily inventory export

ScheduleGET /v1/files

A Zapier Schedule step calling the API with since pushes a daily delta into your warehouse.

Cutting the connection

Everything is revocable instantly, from API & Webhooks. There is no third party holding a session on your behalf: an integration is exactly one API key plus one endpoint URL, both owned by you.

Revoke one key

The trash icon next to a key. Any Zap using it stops authenticating within seconds.

Remove one endpoint

Deletes the subscription. DRIVUNO stops sending events to that URL immediately.

Disconnect everything

One button revokes every key and removes every endpoint at once — the emergency switch.

Rotate rather than share

Never reuse one key across several tools. One key per integration means you can cut Zapier without breaking Make, n8n or your own scripts.

Not just Zapier

The exact same key + endpoint works with any automation platform that can catch a webhook or call a REST API — which is essentially all of them.

Make (Integromat)Custom Webhook module + HTTP module. Same URL, same key.

n8n (self-hosted)Webhook node — ideal if you want automation inside your own network.

Microsoft Power Automate"When an HTTP request is received" trigger.

Slack workflowsWebhook trigger, straight into a channel, no middleman.

Pipedream / Workato / TrayStandard HTTP trigger + Bearer authentication.

Your own backendAny HTTPS endpoint. Signature verification snippet above.

Frequently asked

Can Zapier browse my files or read my documents?
No. A key grants read access to metadata only: identifiers, sizes, folder structure, versions, timestamps. Names arrive encrypted (name_encrypted: true) and contents are never transmitted in readable form. Decryption happens exclusively on your devices, with keys DRIVUNO never receives.
Can Zapier see my email, my password or my team's data?
No password, no recovery material, no message body ever leaves your device unencrypted. The /v1/me endpoint returns your account id, the key's scopes and the API version — nothing else.
How do I know if I'm currently connected?
Open API & Webhooks. The banner at the top states whether an integration is active, how many keys and endpoints exist, and when each one was last used. If it says “No active integration”, nothing external can reach your account.
What happens to running Zaps when I revoke?
They fail immediately with a 401 and Zapier will email you about the erroring Zap. Nothing is deleted on the DRIVUNO side, and no queued event is delivered afterwards.
Is there a rate limit?
600 requests per minute per key. Webhook deliveries are retried on failure; an endpoint that keeps failing is auto-disabled and flagged in the app so a broken Zap never silently drops events.
Do I need the official Zapier app from the directory?
No — and you would gain nothing by waiting for it. The directory listing only replaces the manual URL paste with a branded picker; capabilities are identical because both run on the same API.
Encrypted on your device · upload in 1 click
Upload