Google Drive New File to Teams Notification
When a file is added or updated in a watched Google Drive folder, the flow posts an adaptive card to a Teams channel with the file name, owner, type, and a link, optionally @mentioning a reviewer. Keeps the team instantly aware of new Google Drive content where they work.
Provided as-is, without warranty of any kind. Review and test each pattern in a non-production environment before deploying it to live automations. See our Terms.
Overview
This flow keeps a team instantly aware of new or updated content in a watched Google Drive folder. On a schedule it lists the folder, detects files it has not seen before (de-duplicated via a Dataverse ledger), posts a formatted card-style message to a Microsoft Teams channel with the file name, type, owner, modified date, and a Drive link, and optionally emails a reviewer via Outlook.
Why it matters: New Drive files go unnoticed. Surfacing them in Teams (where the team already works), with a one-click link, removes the "did anyone see this?" gap.
Status: Built as solution FlowLibs - Google Drive New File to Teams Notification (CF-682). Ships Off - go-live requires only connection authorization and environment-variable values.
Use Case
A team collaborating around a shared Google Drive folder (marketing assets, operations docs, intake) wants a Teams heads-up whenever a file lands or changes, plus an optional email to a named reviewer.
Flow Architecture
Recurrence
RecurrencePoll the folder on a schedule (Minute / 5) - Drive has no trigger.
Initialize varCorrelationId
Initialize VariableRun correlation ID (@guid()) for end-to-end tracing.
Initialize varWatchFolderId
Initialize VariableWatched folder id from flowlibs_WatchFolderId.
Initialize varTeamsGroupId
Initialize VariableTarget team id from flowlibs_TeamsGroupId.
Initialize varTeamsChannelId
Initialize VariableTarget channel id from flowlibs_TeamsChannelId.
Initialize varReviewerEmail
Initialize VariableOptional reviewer email from flowlibs_ReviewerEmail (blank = skip).
List Files In Watch Folder
Google Drive - ListFolderList items in the folder (returns a bare BlobMetadata array).
Apply to each File
ForeachProcess each listed item.
Condition Is File
ConditionSkip subfolders; act only on real files (IsFolder == false).
Check Ledger For File
Microsoft Dataverse - ListRecordsLook up ledger by file id + last-modified.
Condition Is New
ConditionEnvironment Variables
| Schema name | Type | Default | Description |
|---|---|---|---|
| flowlibs_WatchFolderId | String | REPLACE_WITH_GOOGLE_DRIVE_FOLDER_ID | Google Drive folder id polled for new/updated files. |
| flowlibs_TeamsGroupId | String | <your-team-id> | Target Teams group/team id. |
| flowlibs_TeamsChannelId | String | <your-channel-id> | Target Teams channel id. |
| flowlibs_ReviewerEmail | String | — | Optional reviewer email (blank = skip the email branch). |
Connectors & Connections
| Connector | API name | Actions used |
|---|---|---|
| Google Drive | shared_googledrive | ListFolder |
| Microsoft Teams | shared_teams | PostMessageToConversation |
| Office 365 Outlook | shared_office365 | SendEmailV2 |
| Microsoft Dataverse | shared_commondataserviceforapps | ListRecords CreateRecord |
All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.
Customization Guide
Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.
- Type filter
- Add a Condition on MediaType (or filename extension) to notify only on certain file types.
- Mention routing
- Map folders to reviewers by extending flowlibs_ReviewerEmail into a lookup, or add multiple recipients.
- Polling cadence
- Change the Recurrence interval (default Minute / 5) to suit latency vs. API-call budget.
- Digest mode
- Accumulate matches and post one periodic summary instead of per-file messages.
- Updates vs. new only
- The ledger keys on file id + last-modified, so edited files re-notify. To notify on new files only, key the dedup on flowlibs_fileid alone.
Key Expressions
The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.
EXPR.01Skip folders
Act only on real files.
EXPR.02Dedup filter
Dedup on file id + last-modified.
EXPR.03Is new
Only notify unseen file versions.
EXPR.04Drive link
Build the one-click Drive link.
EXPR.05Has reviewer
Gate the optional reviewer email.
Customize & download
Generate a ready-to-import copy of this solution with your environment-variable values baked in — available on Base, Pro, or Team.
Upgrade to customize
Comments
Sign in to join the conversation.
Sign inNo comments yet. Be the first to share your experience with this flow.