Connect Jira to Calendarhero

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

View example

Turn Jira customer meeting requests into Calendarhero invites

Create a Calendarhero meeting request when a new Jira issue contains a clear customer meeting request, participants, and a time window.

View example

Check Calendarhero meetings around Jira review dates

When an issue is updated with a review date range, retrieve Calendarhero meetings in that range and include the results in the run report.

View example

Find existing Calendarhero contacts from new Jira requests

Search Calendarhero for a contact named or emailed in a new Jira customer request, then include matching results in the run report.

View example

Schedule Jira project kickoffs when project details are ready

For a newly added Jira project with kickoff participants and an agreed time range in its available details, create a Calendarhero meeting request.

Supported Triggers and Actions

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

Jira triggers

Calendarhero actions

Recurring trigger

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

TriggerScheduled

Add Calendar Connection

Tool to add a calendar integration to a user's account. use after gathering provider credentials.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Contact

Tool to create a new contact. use after confirming contact details before making the api call.

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Create Meeting Request V2

Tool to create a new meeting request in calendarhero. use when scheduling a meeting with participants, time range, and additional details.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Fetch Contact

Fetch contact

ActionInstant

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

TriggerInstant

Fetch Meeting Details

Tool to fetch details for meetings within a specified timeframe. use this after user provides start and end datetimes in iso8601.

ActionInstant

Fetch User Profile

Tool to fetch the profile details of the authenticated user. use after obtaining a valid access token.

ActionInstant

List Meetings

Tool to retrieve the user's meetings within a specified timeframe. use after confirming date range to fetch raw calendar data.

ActionInstant

List Meeting Templates

Tool to list all meeting templates available for quick scheduling. use after authenticating and when you need to retrieve available templates before scheduling.

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.