Algodocs

Log In
Get Started For Free
Book A Demo

Algodocs — Imports, API, Formats, Limits & Folders

Light, modern, and JavaScript-free for maximum compatibility.

Start here

Overview

Bring documents into Algodocs via Manual Upload, Email, Google Drive, Dropbox, Zapier, or the REST API. This page unifies steps, supported formats, practical limits, folder behavior, and guidance for combined PDFs.

At a glance

  • Multiple import channels with extractor selection per flow
  • PDFs & common image types supported
  • No strict hard cap on pages/file size (practical limits may apply)
  • Folders are organizational (no special processing semantics)
Flexible Reliable Mind source clean-up rules

Quick access

Go to Imports API Reference
Ingestion

Import Methods

Pick the method that fits your workflow. Select a destination folder and an Extractor.

Steps

  1. Open File Manager → navigate to your target folder
  2. Right-click → Upload → select file(s)
  3. Choose the Extractor to process the documents
  4. Processing begins after upload

Tips

  • Use subfolders per vendor/customer
  • For very large files, consider API or splitting batches

Filters

  • Type: Sender is / Subject contains / Body contains
  • Value: multiple values via | separator
  • Save in: destination folder in Algodocs
  • Extractor: applied to matching attachments

Why use it

Great for invoices/POs arriving by email — no manual steps once filters are set.

Attachments that match your filters ingest automatically.

Setup

  1. Connect Google Drive in Integrations
  2. Select Drive folder(s) to watch
  3. Pick destination folder + Extractor in Algodocs
  4. Save the integration

Notes

Cleanup: Source files in the watched folder may be removed post-import to prevent duplicates. Use a dedicated “Drop-in” folder.

Polling occurs periodically (e.g., every few minutes).

Setup

  1. Connect Dropbox in Integrations
  2. Choose the Dropbox folder to monitor
  3. Select destination folder + Extractor

Good practice

Use a dedicated ingest folder and keep originals in an archive if needed.

Steps

  1. In Zapier → My Apps → connect Algodocs
  2. Create a Zap: choose a Trigger app (source of files)
  3. Add Algodocs action → send file/URL to folder + Extractor

Why use it

No-code pipelines from 2,000+ apps (email, storage, back-office, etc.).

API Reference

Integrate programmatically with the official API documentation.

Open API Reference
Compatibility

Supported File Formats

PDFs (generated, scanned, mixed) and common image formats.

PDF

  • Text-based PDFs (digital)
  • Scanned PDFs (image-only)
  • Mixed PDFs (text + image)
OCR-readyAny layout

Images

  • PNG
  • JPG / JPEG
  • TIFF
Deskew helps300 DPI ideal
Boundaries

Document Size & Page Limits

General

  • No strict app-level cap on pages or file size
  • Very large single uploads may hit browser/network limits
  • Prefer chunking via integrations/API for mega loads

Throughput Tips

  • Compress scans (300 DPI, grayscale where possible)
  • Batch by vendor/date for clean analytics
  • Automate with Drive/Dropbox/Zapier/API
Organization

Folders in Algodocs

Folders help organize and route imports; they don’t change extraction behavior.

Best Practices

  • One folder per document type or vendor
  • Mirror finance/ops taxonomy (AP, AR, Statements)
  • Attach import flows (email rules/storage) per folder

Access

  • Use folder-level permissions if needed
  • Set default extractor per flow
Multi-doc files

Do I Need to Split a Combined PDF?

Keep combined when…

  • All pages are one case/transaction/vendor
  • You want one output payload per file
  • Extractor handles page variety well
Simpler flow

Split when…

  • Pages mix vendors or document types
  • You need one record per invoice/packet
  • Single file risks timeout → batch it
Pre-process if needed
If bulk PDFs are common, add a pre-step to segment by vendor/reference for cleaner downstreams.
Developers

API

Open API Reference
Help

FAQ

My upload is huge. Should I compress?

Yes — prefer 300 DPI, grayscale if acceptable, and lossless compression. Split mega batches or use API/integrations.

Route different vendors to different extractors?

Yes — use separate folders and attach the right email/storage/Zap flow to each.

Will files remain in my Drive/Dropbox?

Some flows clean up the source folder post-import. Keep originals in an archive or route copies to an “inbox” folder.

Can I monitor ingestion?

Yes — review integration logs and document statuses; add alerts via Zapier or your ops tools.

Scroll to Top