Skip to content
Notis

Bring Cal booking context to a new Jira issue

Start a Jira request with relevant booking context in view, so you can prepare for a customer conversation without searching Cal separately.

Trigger

New Issue

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

Action

Fetch all bookings

Fetches a list of bookings, optionally filtered by status, attendee, date range, or by event/team ids (which must belong to/include the authenticated user respectively), with support for pagination and sorting.

Why this helps

A Jira issue may arrive without the recent meeting context you need, adding another search before you can respond.

  • Look up bookings when a new issue arrives with attendee or date details.
  • Reduce app switching while preparing a response.
  • Review matching booking details in the run report channel.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Cal once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name and prompt.
  • 3In one instruction, ask Notis to fetch Cal bookings relevant to the new issue using available attendee or date details, and report matches without changing them.
  • 4Pick the Jira New Issue trigger and choose where run reports go.
  • 5Test with one real issue that includes details suitable for finding relevant bookings.

Questions about this workflow

What details can help find relevant bookings?

The booking lookup supports filters such as attendee and date range. Provide useful details in the Jira issue or your instruction.

Does this update Jira or Cal bookings?

No. It fetches bookings and reports context; it does not change the Jira issue or booking.

Will every new issue have matching booking context?

No. Results depend on the details available and bookings accessible to your Cal connection.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Jira triggers

Cal actions

Recurring trigger

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

TriggerScheduled

Add member to team

Adds a new member to a specified team within an organization by creating a team membership.

ActionInstant

Webhook trigger

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

TriggerInstant

Add organization attribute option

Adds a new option to an organization's attribute, requiring a display `value` and a `slug` unique for that attribute.

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

Delete oauth client webhook

Permanently deletes a specific webhook subscription of an oauth client in the cal application, stopping its notifications.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Cancel booking via uid

Cancels an existing and active cal.com booking using its unique identifier (uid).

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

Check calendar availability

Retrieves free/busy availability for a specified calendar to aid scheduling without revealing event details; requires an existing, accessible calendar, noting that data granularity can vary.

ActionInstant

Check gcal synchronization status

Call this read-only action to verify the connection and synchronization status of a user's google calendar integration with cal.

ActionInstant

Check ics feed calendar endpoint

Checks an ics feed url (expected as a query parameter) to verify its validity, accessibility, and icalendar data integrity.

ActionInstant

Check Stripe status

Verifies if stripe is correctly connected to the cal scheduling system and functional for processing payments, reporting only on the integration's status.

ActionInstant

Connect any two apps with Notis in the middle.

Jira and Cal, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Cal.