Connect Google Calendar to GitHub

When something happens in Google Calendar, Notis takes the next step in GitHub. 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 Google Calendar to GitHub

View example

Label the GitHub issues you are about to discuss the moment standup is about to start

When your daily standup is minutes away, Notis labels the GitHub issues tied to that meeting so the board already reflects what the team is about to talk through.

View example

Assign GitHub issues to owners the instant a sprint planning event lands on your calendar

When a new sprint planning event is created in Google Calendar, Notis adds the right assignees to the GitHub issues in scope so ownership is set before planning even starts.

View example

Cancel a queued GitHub Pages deployment automatically when the release event is called off

When a release or launch event is cancelled or deleted in Google Calendar, Notis cancels the matching in-flight GitHub Pages deployment so nothing ships that was supposed to wait.

View example

Grant repo access the moment a contributor accepts your pairing session invite

When someone accepts your Google Calendar pairing or onboarding invite, Notis adds them as a GitHub repository collaborator so they can start the second they join.

View example

Add a new hire to the right GitHub team automatically when their onboarding event is booked

When an onboarding event is created in Google Calendar, Notis adds the new teammate to the correct GitHub team so their access is waiting on day one.

View example

Clear stale GitHub Actions caches on a nightly schedule without lifting a finger

On a recurring schedule you choose, Notis clears GitHub Actions caches by key so corrupted or outdated caches never quietly slow down or break your builds.

View example

Confirm private vulnerability reporting is still on across your repos every week

On a weekly schedule, Notis checks whether private vulnerability reporting is enabled on your GitHub repository and reports back, so a security setting never silently drifts off.

View example

Approve a waiting fork pull request workflow run the second your backend gives the go-ahead

When your custom backend or CI tool sends Notis a webhook, Notis approves the pending GitHub Actions run on a fork pull request so trusted contributions stop waiting on a manual click.

View example

Tighten branch protection with extra status checks the moment a code freeze begins

When your code freeze window is about to start on Google Calendar, Notis adds required status check contexts to your protected branch so nothing risky slips in during the freeze.

Supported Triggers and Actions

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

Google Calendar triggers

GitHub actions

Attendee Response Changed

Polling trigger that fires when any attendee's RSVP changes to accepted, declined, or tentative. Returns attendee info and current status.

TriggerPolling

Accept a repository invitation

Accepts a pending repository invitation that has been issued to the authenticated user.

ActionInstant

Event Canceled or Deleted

Triggers when a Google Calendar event is cancelled or deleted. Returns minimal data: event_id, summary (if available), and cancellation timestamp.

TriggerPolling

List repositories starred by the authenticated user

Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.

ActionInstant

Event Starting Soon

Triggers when a calendar event is within a configured number of minutes from starting. Returns event details, time remaining, attendees, and join links when available.

TriggerPolling

List stargazers

Deprecated: lists users who have starred a repository; use `list stargazers` instead.

ActionInstant

Calendar Event Changes

**SOON TO BE DEPRECATED** - Use Calendar Event Sync (polling trigger) instead. Real-time webhook trigger for calendar event changes. Returns event metadata only. For full event data, use Calendar Event Sync (polling trigger).

TriggerInstant

Star a repository for the authenticated user

Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.

ActionInstant

Event Created

Polling trigger that fires when a new calendar event is created. Returns event ID, summary, start/end times, and organizer info.

TriggerPolling

Add email for auth user

Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.

ActionInstant

Calendar Event Sync

Polling trigger that returns full event data including details, attendees, and metadata. For real-time notifications with basic info, use Calendar Event Changes (webhook).

TriggerPolling

Add app access restrictions

Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.

ActionInstant

Event Updated

Triggers when an existing Google Calendar event is modified. Returns the event ID, change type, and the specific fields that changed with their previous and new values.

TriggerPolling

Add a repository collaborator

Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.

ActionInstant

Add a repository to an app installation

Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.

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.