Define what counts as a new file
For the first trial, expect one Slack notification for one PDF newly created in the practice folder. Editing that file should not create another notification. Creating a file, moving an existing file and adding a shortcut are different operations; list each required behavior as a separate acceptance case.
Configure the folder watcher
Use Google Drive > Watch Files in a Folder and select the intended drive, folder, file types and a small limit. Start with By Created Time. By Modified Time suits a different requirement and may include edits or renames. Do not assume recursive subfolder coverage or reliable detection of every move without checking those cases.
Preserve the file identifier
Track the Drive file ID rather than the filename. Two files can have the same name, and one file can be renamed. Prepare a small ledger with file_id, notified_at and slack_message_id. If the goal later changes to revision notifications, define a version or modification-time rule; excluding every previously seen file ID would suppress legitimate updates.
Send a minimal message to a fixed channel
Configure Slack > Send a Message with a practice channel. Map a filename, file ID and returned viewer link into a message such as “New deliverable: TEST-D001.pdf.” If the required link is absent, inspect Get a File/Folder Metadata. Treat supplied filenames as text, not as instructions for choosing a destination or generating mentions.
Keep file sharing separate from notification
Posting the URL does not grant Drive access. Confirm that intended recipients can open it under the existing sharing policy. If they cannot, review the required shares instead of changing the file to public. Check Slack link-preview behavior when the filename and access-controlled link are enough for the notification.
Record success after sending
Store the file ID, notification time and returned message ID after Slack succeeds. Reconcile the ledger and Slack before replaying an ambiguous failure. A lookup followed by a write can race with another execution. Reduce overlapping work or use an appropriate unique-key mechanism rather than presenting a search step as an exactly-once guarantee.
Exercise four distinct operations
Test a newly created PDF, an edit to the same file, a move of an existing file and a separate file with the same name. Write the expected notification count before running them. Compare module outputs with the actual channel and document which test account could view the file; receiving a URL alone is not evidence of access.
Review backlog and timing
Check behavior when arrivals exceed the configured limit and when many files appear between runs. One successful notification does not establish complete coverage. If switching to modified-file monitoring, inspect the larger workload and consumption before expanding the scope.
Start a small workflow in Make
Try the required workflow with practice data, then choose a plan around its usage and features. Check current prices, promotions and eligibility in the official signup flow.
Sign up on MakeAffiliate linkEstimate costs for your workload
Enter monthly jobs, billable steps and retries to see how different billing units affect your estimate.
Open cost calculatorOfficial sources
Pricing, availability and feature limits can change. Check the linked official pages before subscribing.
- Google Drive module referenceInformation checked: 2026-10-29
- Slack message modulesInformation checked: 2026-10-29
- Schedule a scenarioInformation checked: 2026-10-29
- Make pricing — Core at 10,000 monthly creditsInformation checked: 2026-10-28
- Make creditsInformation checked: 2026-10-26
- Make scenario settingsInformation checked: 2026-10-26