Drive import
Connect Google Drive, build an automation with a Drive trigger pointed at a folder, and Document Blueprint pulls new files in automatically through the same downstream pipeline as Gmail intake.
A Drive automation watches a Google Drive folder and imports new files automatically. It uses the same downstream file pipeline as Gmail intake. Any workspace member can create a Drive automation without a role gate.
What you need
You need a connected Google Drive account and the folder you want to watch. Go to Settings > Account and verify the Drive integration row says Connected.
Open the target folder in Google Drive. Copy the last segment of the folder URL to find the Folder ID *.
Build the automation
The Folder name field provides a display label for the automation card. It also acts as a fallback value when a template captures the Drive folder name and the lookup fails.
Trigger settings
The Watch Drive Folder trigger matches files directly inside the specified folder. Files in subfolders are not matched. You must create a separate automation to watch a subfolder.
A new trigger accepts all file types by default. You can restrict ingestion by selecting the PDF and Images chips. You can also type arbitrary MIME types like text/csv using the Custom… option.
Restrict ingestion further using a File name contains filter. This field uses substring matching.
File extraction and routing
Document Blueprint extracts data from PDFs and supported image formats (PNG, JPEG, WebP, HEIC, HEIF, and GIF). The app stores other allowed file types without extraction.
Without an Extraction step, the Mailbox routing row requires you to choose a Document. The automation routes files to the templates associated with that document. When you add the Extraction step, you select a Template. This template may require an Incoming document type selection.
Templates can capture Drive delivery values like the file name, created time, modified time, and folder. A template can use a Drive identifier to route a file to an existing case. Otherwise, the app creates a new case for the file.
Timing and history
The app uses one user-level Drive channel to feed all of your enabled Drive automations. These watch channels expire and renew automatically.
Connecting Drive and saving a Drive automation both register the watch immediately, so matching files start processing into the chosen mailbox within a minute or two. If Google refuses the registration, a daily repair job retries it.
To ingest historical files, open a saved automation and use the Run on past files section. The app processes historical files 50 at a time.
The automation skips unchanged files on reruns. A modified file updates its modified time and processes again. Per-case duplicate detection also skips an existing file ID. A file whose processing failed is retried automatically on the next Drive change or past-files run, up to three times.
If you disconnect Google Drive, or Google revokes the app's access, the automation pauses. The automation card shows a Google Drive is not connected banner. Click Connect to authorize the account again. A Drive automation saved before Drive is connected shows the same banner and turns on when you connect. Automations that paused because of the lost connection turn back on by themselves; ones you paused yourself stay off.
Import a local folder
To import local files manually, open the chat and click Import a folder from the plus menu. This flow accepts PDFs only and imports a maximum of 15 files at once.
Browsing a Drive folder lists up to 1,000 items.