Keep Jira work aligned with calendar changes
When plans shift on your calendar, give Notis an instruction for updating the Jira issue tied to that commitment.
Trigger
Calendar Event Changes
Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.
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 meeting or deadline changes in the calendar, but the related Jira ticket still reflects the old plan until someone remembers to update it.
- Surface schedule changes in the relevant Jira work item.
- Reduce the gap between calendar decisions and project tracking.
- Keep important dates and context together for the team.
Setup
Build it in a few focused steps.
- 1Connect Outlook and Jira once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis what you want from any channel.
- 3In one instruction, explain how Notis should identify the related Jira issue and summarize a changed calendar event in that issue.
- 4Choose the Outlook Calendar Event Changes trigger and select where run reports should go.
- 5Test with one real calendar change and check the Jira update.
Questions about this workflow
Can Notis match a calendar event to its Jira issue automatically?
Tell Notis what identifying details to use, such as a Jira key in the event title or description. If the event does not provide enough information, Notis may need your instruction to handle that case.
Does this trigger cover deleted events?
The listed Calendar Event Changes trigger covers events that are created, updated, or deleted. Explain how Notis should handle each change type.
What if no related issue can be identified?
Include a fallback in your instruction, such as reporting that no matching issue was found, rather than making an unsupported update.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Outlook to Jira. A trigger fires from one place; an action lands in another.
Outlook 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.
New Contact Added
Triggered when a new contact is added in the Outlook contacts.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Calendar Event Changes
Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
New Calendar Event
Triggered when a new calendar event is created in the Outlook calendar.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
New Outlook Message
Triggered when a new message is received in the Outlook mailbox.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
New Sent Message
Triggered when a new message is sent from the Outlook mailbox.
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.
Outlook 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.