Triggers

A trigger is what an automation watches. Two kinds: Gmail and Drive. Filters are AND-logic — every condition has to match — and the first matching automation wins, so order specific automations before broad ones.

What you need

• A connected integration for the source you want to use.

Gmail

Pulls messages from the connected user's Gmail using whichever filters you set:

• Subject contains — case-insensitive substring on the message subject (e.g. invitation to bid).
• Sender contains — substring on the From address (e.g. @vendor.com).
• Gmail label — the label name as it appears in Gmail (e.g. Paperwork/Invoices).
• Read status — All, Unread only, or Read only.
• Capture From Email — pills for Sender, Subject, Body, Files. They control what the automation pulls into the pipeline; Sender, Subject, Files are on by default. Turn Body on only when an extraction template uses email_body_context fields.

Use Gmail for inbound document email — vendor invoices, signed PDFs returning from clients, RFP responses.

Drive

Watches a Google Drive folder for new files:

• Folder ID — paste the ID from the Drive folder URL (required).
• Folder name — display only; doesn't affect matching.
• File name contains — substring on the file name (e.g. INV-2026).
• MIME types — comma-separated allow-list (e.g. application/pdf, image/png).

Use Drive for shared-folder workflows where files are dropped in, or for routing files out of other Drive-based systems.

GmailSubject contains 'invitation to bid', Files captured

DriveFolder Vendor Onboarding, application/pdf only

Tips

Related

• Creating an automation
• The action pipeline
• Google Drive import