Connect Google Calendar to Circleci

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

View example

Start a CircleCI build from a new calendar event

Turn a newly created calendar event into a CircleCI pipeline run when it signals planned release or delivery work.

View example

Check CircleCI job status before a meeting

Before a scheduled meeting starts, retrieve the relevant CircleCI job details so build status and timing are ready for review.

View example

Review pipeline workflows after a calendar change

When an event's details change, look up the associated CircleCI pipeline workflows to help spot delivery plans that may need attention.

View example

Launch a CircleCI build when a key attendee accepts

Use an attendee's accepted RSVP as a signal to start a related CircleCI pipeline for a scheduled delivery session.

View example

Check recent pipelines after a delivery event is canceled

When a delivery-related calendar event is canceled, list recent project pipelines to help review build activity that may need follow-up.

View example

Get a scheduled overview of CircleCI pipelines

On a recurring schedule, list pipelines for a chosen CircleCI project and send a concise run overview to your report channel.

View example

Fetch CircleCI configuration when a release is requested

Use an incoming webhook request to retrieve the configuration for a specified CircleCI pipeline when release context is needed.

View example

Review CircleCI test results for a scheduled work item

Use full calendar event data to identify a related CircleCI job and retrieve its test metadata for a focused follow-up.

View example

Check CircleCI self-hosted runners on a schedule

Periodically list configured self-hosted runners so teams can keep runner availability visible in their routine operations review.

Supported Triggers and Actions

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

Google Calendar triggers

Circleci actions

Recurring trigger

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

TriggerScheduled

Get Job Artifacts

Tool to retrieve artifacts produced by a specific job. use after a job has completed to list its output files.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Job Details

Tool to fetch details of a specific job within a project. use when you need status, timing, and executor information for a circleci job by its number.

ActionInstant

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

Get Pipeline Config

Tool to fetch pipeline configuration by id. use when you need the source or compiled yaml of a specific pipeline.

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

Get Test Metadata

Tool to fetch test metadata for a specific job. use when you need detailed test results, run times, and failure messages after a job completes.

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

Get User Information

Tool to retrieve information about a circleci user by their unique id. use when you need user profile details after obtaining the user id.

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

List Pipelines for Project

Tool to list all pipelines for a specific project. use when you need to retrieve the pipelines for a project (e.g., to display recent runs on a dashboard).

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

List Self-Hosted Runners

Tool to list available self-hosted runners. use when you need to retrieve all configured self-hosted runners for your organization.

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

List Workflows by Pipeline ID

Tool to list all workflows associated with a specific pipeline. use when you need to fetch or paginate through workflows by pipeline id.

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.