Automations & Integrations

Connect Gmail, build an automation whose trigger matches the messages you want, and Document Blueprint pulls each match in — categorizing, extracting, and filing it to a case without manual upload.

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.

In the Automations drawer, click + New Automation, fill the Trigger, Destination, and (optionally) Extract Data nodes, then Save. The automation runs on the next matching item.

A trigger is what an automation watches. Two kinds: Gmail (subject contains, sender contains, label, read status) and Drive (folder ID with optional filename and MIME filters).

When the trigger matches, the automation downloads the file, finds or creates the right case, saves the file with its category and provenance, and (if a template is set) runs extraction inline so the case fields are populated immediately.

When you turn on Extract Data and pick a template, the automation links to that template's workspace document source — and the source's file category becomes the tag applied to every ingested file.

Open the Automations drawer to see every automation in the workspace. Each card shows the trigger, the destination mailbox, the last-run state, and a toggle to enable or disable it. Open a card to edit, backfill, or delete.

Open the automation and read its Activity log under the canvas. Each entry is one item the automation processed, with the resolved case ID and any error. Almost every "why didn't this fire?" question is answered there.

Connect Google Drive, build an automation with a Drive trigger pointed at a folder, and Document Blueprint pulls in new files automatically — same downstream pipeline as Gmail intake.