Update Jira issues when meeting details change
Keep Jira work aligned when a meeting moves or its booking details change.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Edit Issue
Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.
Why this helps
A changed meeting can leave Jira tickets carrying stale timing or coordination details.
- Refresh issue details after a relevant booking change.
- Keep meeting coordination context attached to tracked work.
- Reduce manual edits after schedule changes.
Setup
Build it in a few focused steps.
- 1Connect Cal and Jira once in the Notis portal.
- 2Create an automation from any channel or in Automations, New Automation.
- 3Tell Notis to update the identified Jira issue with changed booking details that affect its coordination.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real meeting change and inspect the updated issue.
Questions about this workflow
Does Cal send a change event to this workflow?
No Cal trigger events are listed. A webhook request containing the change starts the automation.
Will Notis update every ticket related to the meeting?
It can update the issue identified by the request and instruction. Supply enough context to identify the intended issue.
What if the change does not affect the work?
The instruction can tell Notis to leave the issue unchanged unless the submitted change matters to its coordination.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cal to Jira. A trigger fires from one place; an action lands in another.
Cal triggers
Jira actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Attachment
Uploads and attaches a file to a jira issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Cal and Jira, 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 Jira.