Narrow scopes over domain-wide delegation
Domain-wide delegation is the fastest way to make a Workspace integration work and the hardest to justify afterwards, because it grants an automation the ability to act as any user in the domain. Most workflows do not need it: a dedicated automation account added to the specific shared inbox, Drive folder or calendar it operates on covers the same ground with a fraction of the blast radius. We use delegation only where an API genuinely offers no alternative, document why in the scope matrix, and keep the granted scopes to the narrowest set that makes the workflow run.
Watches expire, quotas differ, ownership matters
Gmail and Drive push notifications are subscriptions that expire and must be renewed on a schedule; a workflow that silently stops days after launch is almost always a lapsed watch. Quotas differ substantially between APIs, so a design that is comfortable against Gmail can hit a wall against Drive. Shared Drive ownership needs deciding explicitly, since files created by an automation under the wrong identity become inaccessible when that account is removed. None of these are difficult, but all three are invisible until they break, so they go into the runbook rather than into folklore.
Recover missed Gmail and Drive events without broad access
For a shared inbox or Drive folder workflow, normalize each notification to the dedicated account, mailbox or folder, stable message or file ID, version marker and event time. Recheck the user's access and current item state before creating a ticket or processing a document, then deduplicate on the source ID and version so a replay cannot repeat the action. Store a checkpoint for completed items and run a bounded reconciliation scan after a watch renewal or delivery gap; send inaccessible, changed or ambiguous items to their owner. Estimate quota use from representative volumes rather than a short test, and pause work when limits are reached instead of dropping the cursor. The runbook names the mailbox/Drive owner, watch-renewal owner, exception reviewer and steps to revoke the automation account's access.
How to measure the pilot
A pilot is accepted against the current process, not an industry promise. Agree the sample, baseline and owner before launch, then review the same measures after the workflow has handled real cases.