What automations are
An automation watches Gmail or Google Drive for a specific kind of file and routes each match into a workspace mailbox — tagging it with a category, optionally extracting fields with a template, and creating or updating the matching case.
Last updated
An automation watches Gmail or Google Drive for a specific kind of file and routes each match into a workspace mailbox — tagging it with a category, optionally extracting fields with a template, and creating or updating the matching case. It's how documents arrive in Document Blueprint without anyone clicking upload.
What you need
- A workspace with at least one connected integration (Gmail or Drive)
The shape of an automation
Every automation has three nodes in the builder:
Trigger — what to watch.
- A Gmail trigger filters by subject contains, sender contains, label, and read status.
- A Drive trigger watches a Google Drive folder and can filter by filename and MIME type.
Destination — where the match lands. The mailbox the case appears in, the file category tag (when extraction is off), and a duplicate-handling rule (Skip duplicate, Re-extract, Create new) that controls what happens when the same source file shows up twice.
Extract Data (optional) — a template that runs extraction inline. When extraction is on, the template's linked workspace document source supplies the file category automatically; the standalone category selector hides.
Why automations matter
Without automations, every document is uploaded by hand. With one in place, the documents flow in on their own and the team's attention shifts from logistics to the actual work. A workspace processing 200 documents a week saves hours of clicking every week.