Appearance

Cloud storage ​

To land approved documents in Google Drive, Dropbox, SharePoint, or OneDrive, you orchestrate it from Recognito's outbound channels — a webhook to a small receiver that writes to your storage, or a Make.com / n8n scenario using their cloud-storage nodes. You wire the destination; Recognito sends the file.

This page covers the two patterns and how to plan the archive.

What this is for ​

  • Compliance archiving. Regulated industries often need original documents in long-term storage.
  • Team-shared archives. Your AP team wants approved invoices in a shared folder for easy retrieval.
  • Backup alongside the data. Recognito holds the structured data; cloud storage holds the original PDFs.

For each, the goal is the same: when a document is approved, the original file lands in a cloud-storage location you control.

Pattern 1 — Webhook + receiver ​

The simplest reliable path.

  1. Settings → Integrations → Webhook Integration. Configure a webhook firing on Document Approved with Include document files turned on, so the payload carries the PDF.
  2. Build a small receiver — a serverless function or a small service — that accepts the POST and uses your cloud storage's SDK to upload the file.

The receiver handles auth to your storage, picks the destination folder (often from document metadata), and writes the file plus any structured data.

Pattern 2 — Make.com or n8n ​

If your team already runs Make or n8n, skip the receiver:

  1. Add Recognito's node as the trigger or source step.
  2. Add the storage node — Google Drive, Dropbox, SharePoint, and OneDrive all have mature nodes on both platforms.
  3. Map the fields and set the destination inside the scenario.

Make and n8n handle the auth and upload; you just orchestrate. See Make.com and n8n.

Plan the folder structure first ​

Whichever pattern you pick, decide the layout before going live:

  • Flat by project — every document in one folder. Simple, but unwieldy at scale.
  • Hierarchical by date — year / month / day. The standard archive pattern.
  • Hierarchical by vendor — vendor → year / month. Useful for vendor-centric audits.
  • By legal entity — subsidiary → year / month. For multi-company setups.

The right pattern depends on how you'll search the archive later. Moving files between folders afterward is heavier than getting it right from the start.

What's next ​