Import help

Document grouping during import

The default Rowvia workflow is one document as one row. When importing a folder or ZIP, you can also combine multiple sources into one row before upload.

Open app Integration docs
Rules

Which grouping rule to choose

The import preview shows proposed rows before upload. If the rule does not fit the file structure, change it in the preview before confirming.

One file per row

One file per row

Use this for ordinary imports of independent documents.

Setting
One file per row
Input
  • invoice-001.pdf
  • invoice-002.pdf
Result
  • invoice-001.pdf -> 1 row
  • invoice-002.pdf -> 1 row

Top-level folder

Top-level folder

Best for multiple files belonging to one applicant, client, or project.

Setting
Top-level folder
Input
  • 01-anna-novakova/cover-letter.txt
  • 01-anna-novakova/resume.pdf
  • 02-petr-horak/resume.pdf
Result
  • 01-anna-novakova -> 2 sources in one row
  • 02-petr-horak -> 1 source in one row

Folder depth

Folder depth: 2

Use this when the first folder is a batch and the next level identifies the row.

Setting
Folder depth: 2
Input
  • export/client-a/contract.pdf
  • export/client-b/contract.pdf
Result
  • client-a -> contract.pdf
  • client-b -> contract.pdf

Same basename

Same basename

Use this when sidecar files share the same base filename.

Setting
Same basename
Input
  • case-1.pdf
  • case-1.txt
  • case-2.pdf
Result
  • case-1 -> PDF + TXT
  • case-2 -> PDF

Path template

Path template

Use this for a readable rule with a named path part.

Setting
Path template
Pattern
{applicant}/*
Input
  • 01-anna-novakova/cover-letter.txt
  • 01-anna-novakova/resume.pdf
Result
  • 01-anna-novakova -> both files

Template for one document type

Path template

Useful when rows should be created only from one specific file inside each folder.

Setting
Path template
Pattern
clients/{client}/contract.pdf
Input
  • clients/acme/contract.pdf
  • clients/acme/notes.txt
  • clients/contoso/contract.pdf
Result
  • acme -> contract.pdf
  • contoso -> contract.pdf
  • notes.txt stays unmatched

Regex capture

Regex capture

Use this for strict validated formats that a path template cannot describe precisely.

Setting
Regex capture
Pattern
^(case-[0-9]+)/
Input
  • case-1/contract.pdf
  • case-2/invoice.pdf
  • loose.pdf
Result
  • case-1 -> contract.pdf
  • case-2 -> invoice.pdf
  • loose.pdf stays unmatched

Path template

  • A named part in braces, for example {applicant}, becomes the row name.
  • * matches any text inside one path segment and does not capture it.
  • ** also matches nested folders.
  • The template is matched against the full relative path and is case-insensitive.

Practical guidance

  • For normal applicant, client, or project folders, choose Top-level folder.
  • Use Path template when only a specific document type should create rows or when a named path part is clearer than a folder-depth rule.
  • Keep Regex capture for cases that need strict format control.