Connect AssemblyAI to Google Drive

When something happens in AssemblyAI, Notis takes the next step in Google Drive. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from AssemblyAI to Google Drive

View example

Save completed AssemblyAI transcripts to Drive

Turn a completed AssemblyAI transcript into a searchable Google Drive document.

View example

File transcripts with source details

Create a Drive file with transcript text and the source details included in a completed-transcription payload.

View example

Add a review note to a transcript file

Attach a review comment to a Drive file when a completed transcription payload identifies the file and note.

View example

Share a transcript with its reviewer

Grant a specified reviewer access to an existing Drive transcript file using details in a webhook payload.

View example

Create a project folder for a transcript

Create a Google Drive folder for the project named in a completed-transcription payload.

View example

Save a scheduled transcript digest

Create a Drive document summarizing the completed transcripts available to Notis at the scheduled run.

View example

Maintain a transcript follow-up register

Create a scheduled Drive register of transcript follow-ups from source material available to Notis.

View example

Save a weekly transcript topic review

Summarize recurring themes across available transcripts for the review period and save them to Drive.

Supported Triggers and Actions

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

AssemblyAI triggers

Google Drive actions

Recurring trigger

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

TriggerScheduled

Add file sharing preference

Modifies sharing permissions for an existing google drive file, granting a specified role to a user, group, domain, or 'anyone'.

ActionInstant

Webhook trigger

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

TriggerInstant

Copy file

Duplicates an existing file in google drive, identified by its `file id`.

ActionInstant

Create Comment

Tool to create a comment on a file. use when you need to add a new comment to a specific file in google drive.

ActionInstant

Create Shared Drive

Tool to create a new shared drive. use when you need to programmatically create a new shared drive for collaboration or storage.

ActionInstant

Create File or Folder

Creates a new file or folder with metadata. use to create empty files or folders, or files with content by providing it in the request body (though this action primarily focuses on metadata creation).

ActionInstant

Create a File from Text

Creates a new file in google drive from provided text content (up to 10mb), supporting various formats including automatic conversion to google workspace types.

ActionInstant

Create a folder

Creates a new folder in google drive, optionally within a parent folder specified by its id or name; if a parent name is provided but not found, the action will fail.

ActionInstant

Create Reply

Tool to create a reply to a comment in google drive. use when you need to respond to an existing comment on a file.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.