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.
Updated 1 min read
What you need
Any workspace member can create a Drive automation; there is no role gate. You also need the Google Drive folder you want to watch and its Folder ID: the last segment of the folder URL (e.g. 1A2bC_dEfGhIjK).
Step by step
1In Settings -> Account, turn on the Drive toggle row and grant access in the Google sign-in that opens
2Click the Automations button at the bottom of the workspace sidebar to open the Automations drawer, then click New Automation
3On the Trigger node, pick Drive and paste the Folder ID. The optional Folder name is display only (useful for scanning the cards list later)
4(Optional) Add a File name contains filter (e.g. INV-2026) and restrict File types: use the PDF / Images chips or add arbitrary types via Custom… (e.g. text/csv). Gemini AI-extracts PDFs and images; other types are stored without extraction
5On the Destination node, pick the mailbox and choose File storage (Firebase / Google Drive / Both), where ingested files are kept
6(Optional) Turn on Extract Data and pick the template that should run on the file
7Save, then drop a test file into the folder. Within a minute it appears in the destination mailbox
Files already imported from the folder are skipped automatically on re-runs.
TriggerDrive folder Vendor Onboarding
File typesPDF only
DestinationVendor mailbox
ExtractW-9 Intake template
Folder scope and overhead
A Drive trigger matches only files dropped directly inside the folder you specified. Files in subfolders are not matched. To watch a subfolder, point a separate automation at it.