Update Jira when meeting details change
When the meeting moves, update its related Jira ticket with the new details so nobody prepares from stale information.
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
Rescheduled meetings leave old dates and attendance details scattered across tickets and notes.
- Reflect changed meeting details in the related issue.
- Keep preparation work tied to the current meeting time.
- Avoid relying on outdated notes.
Setup
Build it in a few focused steps.
- 1Connect Calendarhero and Jira once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to update the related Jira issue when a meeting-change request arrives, using the revised details included in the request.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test it with one real meeting change request.
Questions about this workflow
How does Notis find the related Jira issue?
Include the Jira issue key in the webhook request, or provide enough identifying context for Notis to find the issue. The workflow cannot infer a relationship that is not supplied or discoverable.
Can it detect reschedules inside Calendarhero by itself?
No. The webhook must be sent to start the automation. Include the changed meeting details in its request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Calendarhero to Jira. A trigger fires from one place; an action lands in another.
Calendarhero 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.
Calendarhero 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.