Connect Codemagic to Google Drive

When something happens in Codemagic, 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 Codemagic to Google Drive

View example

Save Codemagic build release notes to Drive

Turn a Codemagic build completion request into a searchable release notes document in Google Drive.

View example

Create a Drive brief for failed Codemagic builds

Save the failure details sent by Codemagic as a focused troubleshooting brief in Drive.

View example

Log Codemagic deployments in Drive

Create a Drive deployment record from the app version and environment details sent by Codemagic.

View example

Save a daily Codemagic pipeline digest

On a schedule, summarize the Codemagic pipeline information available to Notis in a daily Drive document.

View example

Create a weekly Codemagic build review

Turn the Codemagic build and pipeline information available to Notis into a weekly review document in Drive.

View example

Create a Drive folder for a Codemagic project build

Create a project folder in Drive when a Codemagic build request arrives with a project identifier.

View example

Attach build metadata to a Drive file

Add a custom property to a Drive file using build details supplied in a Codemagic webhook request.

View example

Add a Codemagic review note to a Drive file

Add a concise review note to a specified Drive file when a Codemagic request includes build context.

View example

Share a release file from a Codemagic request

Grant a specified person access to a Drive release file using permission details supplied in a webhook request.

Supported Triggers and Actions

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

Codemagic 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

Change who can access a file by updating its sharing permissions.

ActionInstant

Webhook trigger

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

TriggerInstant

Copy file

Create a copy of an existing file in the same folder.

ActionInstant

Insert File Parent (v2)

Adds a parent folder to a file.

ActionInstant

Create Comment

Add a comment to a file.

ActionInstant

Insert Property (v2 API)

Adds or updates custom metadata on a file.

ActionInstant

Create Shared Drive

Create a shared drive for collaboration or storage.

ActionInstant

Batch Get Spreadsheet Values

Reads multiple ranges from one spreadsheet in a single request.

ActionInstant

Create File or Folder

Create a file or folder, optionally with uploaded content.

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.