Connect Google Calendar and Jira to power automations.

Trigger from one app, act on another, with a thinking brain in the middle. Build it in plain English. Approve from your phone.

When this happens · Trigger

Do this · Action

Build an automation Browse templates

Popular workflows

Most used workflows for Google Calendar + Jira

Details

Auto-Create Jira Issues from New Calendar Events

Each new Google Calendar event automatically generates a Jira issue, eliminating duplicate effort when context switches between planning and tracking.

Details

Auto-Assign Jira Tasks When Attendees Accept Calendar Invites

When someone accepts your calendar invite, Notis automatically assigns them the related Jira task—no follow-up message needed.

Details

Transition Jira Issues When Meetings Start

As your calendar event approaches, Notis automatically moves the related Jira issue to In Progress, keeping your board in sync with your actual schedule.

Details

Mark Jira Issues When Calendar Events Are Cancelled

When a calendar event is cancelled, Notis updates the related Jira issue with a status note, so your team knows the work was deprioritized.

Details

Comment on Jira Issues When Calendar Events Are Updated

When you update a Google Calendar event (time, attendees, description), Notis posts the changes as a comment on the related Jira issue for full visibility.

Details

Move Jira Issues to Sprint When Calendar Event Syncs

Notis uses full calendar event data to intelligently move related Jira issues into the active sprint, keeping your board in sync with your scheduled work.

Details

Auto-Create Multiple Jira Tasks from One Calendar Event

A single calendar event can spawn multiple Jira tasks—e.g., a design review creates tasks for feedback, revision, and approval—reducing manual task creation.

Details

Comment on Jira When Attendees Change Their Calendar RSVP

When an attendee changes their RSVP (yes to no, tentative to yes, etc.), Notis posts a comment on the related Jira issue to keep the team informed of availability changes.

Details

Send Jira Notifications When Meetings Are About to Start

As your calendar event approaches, Notis sends a notification for the related Jira issue, ensuring the team has context before the meeting begins.

Supported Triggers and Actions

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

Google Calendar triggers

Jira 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

Add Attachment

Uploads and attaches a file to a jira issue.

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

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

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

Add Watcher to Issue

Adds a user to an issue's watcher list by account 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

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

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

Bulk Create Issues

Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

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

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

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

Link Issues

Links two jira issues using a specified link type with optional comment.

ActionInstant

Create Project

Creates a new jira project with required lead, template, and type configuration.

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.