Confirm a Cal booking when Jira approval arrives
Let an approval update in Jira finish the scheduling loop for a pending Cal booking, using its booking UID as the link between the two.
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
Confirm booking by uid
Confirms an existing booking by `bookinguid` if the booking exists and is in a state allowing confirmation (e.g., not already cancelled or confirmed); this finalizes the booking, does not modify its details, and should typically be performed once.
Why this helps
An approved request can still require a separate Cal visit to confirm the booking, leaving a meeting in limbo.
- Reduce manual follow-up after an approval is recorded.
- Use the booking UID to identify the intended Cal booking.
- See the confirmation result in the selected Notis 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 confirm the pending Cal booking only when the updated Jira issue signals approval and includes its booking UID.
- 4Pick the Jira Updated Issue trigger and choose where run reports go.
- 5Test with one real approval issue and a pending Cal booking that can be confirmed.
Questions about this workflow
What does the Jira issue need to include?
It needs to provide the booking UID, and the issue update needs to indicate approval. State clearly how Notis should recognize approval in your prompt.
Can this confirm a cancelled booking?
No. Cal confirmation applies only when the booking is in a state that allows confirmation, such as awaiting confirmation.
Does this change the booking details?
No. The Cal action confirms the existing booking and does not modify its details.
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.