Keep the team informed about relevant Drive changes
Ask Notis to distinguish useful project changes from routine activity and share only the context your team needs.
Trigger
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Action
Send Message
This tool allows sending a message through dailybot to either specific users or channels/rooms. the message can include markdown formatting.
Why this helps
A stream of file activity can bury the few changes that affect an active project or shared resource.
- Make relevant changes easier to scan in Dailybot.
- Keep routine activity from becoming unnecessary noise through your instruction.
- Include source details available from the change event.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Dailybot once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis what you want from any channel.
- 3Describe which changes matter to your team and ask Notis for a concise message with the affected item and available context.
- 4Pick the Google Drive Changes trigger and choose where Notis run reports should go.
- 5Test with one real change and refine your instruction if the message is too broad or too narrow.
Questions about this workflow
Can this combine changes into a scheduled digest?
This workflow starts when Drive changes are detected. A recurring schedule is a separate Notis trigger and would require a suitable source of change data for that schedule.
Can it identify which project a file belongs to?
Only when the file details or available context make that clear. If project context is missing, ask Notis to leave it unspecified.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Dailybot. A trigger fires from one place; an action lands in another.
Google Drive triggers
Dailybot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Find User by UUID
This tool allows you to find and retrieve information about a specific user in dailybot. it uses the provided user uuid to lookup the user and returns detailed information including the user's uuid, full name, image, username, occupation, birth date, chat platform data, and organization details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Find Workflow by Name
This tool allows users to find a specific workflow within dailybot by providing the workflow name. it returns detailed information including the workflow id, workflow name, workflow status, workflow type, created at, and updated at. it is especially useful to locate a workflow before running or modifying it.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Get All Users
This tool retrieves a list of all users within the organization from dailybot. it doesn't require any input parameters other than authentication. the returned json contains user details including uuid, active status, full name, and organizational data.
File Created
Triggers when a new file is created in Google Drive.
Get Workflows List
This tool retrieves a list of all workflows that the authenticated user has access to in dailybot. it can be executed independently with only the authentication required, and it supports optional pagination parameters (page, per page) to refine the response.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Give Kudos to Users
This tool allows giving kudos to one or multiple users in dailybot. kudos can be given either on behalf of dailybot or the api key owner.
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
Send Message
This tool allows sending a message through dailybot to either specific users or channels/rooms. the message can include markdown formatting.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Connect any two apps with Notis in the middle.
Google Drive and Dailybot, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Dailybot.