Skip to content
Notis

Give matching Drive files a dedicated review thread

When a file matching your Drive query appears, give its discussion a clear home. Notis can create a Discord thread and include the available file context.

Trigger

New File Matching Query

Triggers when a new Google Drive file matches a provided query. This is the legacy query-centric trigger: it preserves Drive API query config such as ``corpora`` / ``driveId`` aliases and emits the historical ``file_matching_query`` event type. ``FileCreatedTrigger`` covers the broader "new file" case and emits ``file_created``.

Action

Create new thread in channel

Creates a new thread in a text or announcement discord channel; requires a 'name' and optionally other details (e.g., 'auto archive duration', an initial 'message') in the request body.

Why this helps

Files that need review can get buried in a busy channel without a dedicated place for discussion.

  • Give relevant files a focused place for discussion
  • Keep review messages together in a thread
  • Reduce channel noise while making follow-up easier

Setup

Build it in a few focused steps.

  • 1Connect Google Drive and Discordbot once in the Notis portal.
  • 2Create an automation in Automations, New Automation, or tell Notis from any channel.
  • 3In one instruction, ask Notis to create a named Discord thread when a matching file appears and include its available link and context.
  • 4Pick the New File Matching Query trigger and choose where run reports go.
  • 5Test with one real file that matches the query and review the thread.

Questions about this workflow

How are matching files selected?

The trigger uses the Google Drive query configuration selected for this trigger.

Does the workflow create a thread for an existing file?

This trigger is for a new Drive file that matches the provided query.

Can the thread include the file link?

Ask Notis to include the link when the event provides it.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Google Drive to Discordbot. A trigger fires from one place; an action lands in another.

Google Drive triggers

Discordbot actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add recipient to group channel

Adds a user to a discord group direct message (dm) channel.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Update guild member information

Adds a user (who is not already a member) to a guild using their `access token` (which must have `guilds.join` scope), optionally setting nickname, roles, mute/deaf status, or flags.

ActionInstant

Comment Added (Docs/Sheets/Slides)

Triggers when a new comment is added to Google Docs, Sheets, or Slides.

TriggerPolling

Assign role to guild member

Assigns a role to a guild member, provided the bot has 'manage roles' permission in the guild and the role to be assigned is hierarchically lower than the bot's highest role.

ActionInstant

File Created

Triggers when a new file is created in Google Drive.

TriggerPolling

Add reaction to message

Adds an emoji reaction from the authenticated user/bot to a specific message in a discord channel; does not return information about existing reactions.

ActionInstant

File Deleted or Trashed

Triggers when a file is moved to trash or permanently deleted in Drive.

TriggerPolling

Add or update thread member

Adds a user to a specific, unarchived thread; the user must have access to the thread's parent channel, and for private threads, the bot must already be a member.

ActionInstant

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.

TriggerPolling

Modify guild ban settings

Permanently bans a user from a discord guild, optionally deleting their recent messages (specify deletion period in seconds or days, not both).

ActionInstant

File Updated

Triggers when a file's metadata or content changes in Google Drive.

TriggerPolling

Bulk ban users in guild with message deletion option

Bans up to 200 users from a discord guild, optionally deleting their recent messages; the bot must have 'ban members' permission in the guild, and this action is irreversible.

ActionInstant

Google Drive Changes

Triggers when changes are detected in a Google Drive.

TriggerPolling

Bulk delete messages in channel

Atomically bulk deletes messages in a discord channel for moderation or maintenance; deletion may not be instantaneous and messages are unrecoverable.

ActionInstant

Connect any two apps with Notis in the middle.

Google Drive and Discordbot, 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 Discordbot.