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 pipeline finds or creates a case using the identifier, routes it to a mailbox, saves the file, and runs extraction. You configure the destination parameters.

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 row and read its Activity log under the canvas to debug a missed run.

Files are routed by a category tag that names the document type. The app tags files when an automation ingests them or a template generates them. You can also name categories in a template or apply them to case files.