Cancel a Cal booking from an explicit Jira request
Keep a cancellation request and its Cal booking together by acting only when the Jira update clearly requests cancellation and supplies the booking UID.
Trigger
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.
Action
Cancel booking via uid
Cancels an existing and active cal.com booking using its unique identifier (uid).
Why this helps
A cancellation can be missed when the request lives in Jira but the booking must be found and cancelled separately in Cal.
- Respond to explicit cancellation requests without switching apps.
- Use the booking UID to target the intended active booking.
- Keep a run report of the cancellation outcome.
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 cancel a Cal booking only when an updated issue explicitly requests cancellation and provides the booking UID.
- 4Pick the Jira Updated Issue trigger and choose where run reports go.
- 5Test with one real issue containing an authorized cancellation request and a valid active booking UID.
Questions about this workflow
Will any Jira update cancel a booking?
The trigger fires for issue changes in the configured project. Your instruction should require a clear cancellation request and a booking UID before acting.
Can the booking be restored afterward?
The action cancels an active booking. Treat cancellation as consequential and verify the request and UID in the issue before enabling the automation.
What if the booking UID is missing or invalid?
The action needs the booking UID. Ask Notis to report that it cannot proceed when the UID is absent or the booking cannot be found.
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.
Add member to team
Adds a new member to a specified team within an organization by creating a team membership.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add organization attribute option
Adds a new option to an organization's attribute, requiring a display `value` and a `slug` unique for that attribute.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Delete oauth client webhook
Permanently deletes a specific webhook subscription of an oauth client in the cal application, stopping its notifications.
New Project
Triggered when a new project is added in Jira
Cancel booking via uid
Cancels an existing and active cal.com booking using its unique identifier (uid).
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.
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.
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.
Check ics feed calendar endpoint
Checks an ics feed url (expected as a query parameter) to verify its validity, accessibility, and icalendar data integrity.
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.
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.