Automations & Documents

An automation watches Gmail or Google Drive and routes each matching file into a workspace mailbox: tagging it with a category, optionally extracting fields with a template, and creating or updating the matching case without manual upload.

A trigger is what an automation watches (Gmail, Drive, Time, or Case Data), and a rule binds that trigger to a destination, optional extraction, and file storage; create one in the Automations drawer.

When a trigger matches, the automation downloads the file, finds or creates the case by identifier, moves that case into the destination mailbox, saves the file with its category, and runs extraction if a template is set.

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.

Open the Automations drawer to manage every automation, then open a card and read its Activity log under the canvas to debug almost any "why didn't this fire?" question.

Every file carries a category, the workspace-scoped join key that decides which templates can process it, which automation tagged it, which case it joins, and which audiences see it.