Skip to content
Notis

Record why a commitment moved in Jira

A changed date is easier to understand when the reason travels with it. Have Notis add that context to the related Jira issue.

Trigger

Calendar Event Changes

Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.

Action

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

Why this helps

A deadline or meeting moves, but teammates see only a different date and have to ask what caused the change.

  • Explain schedule changes where the team tracks delivery.
  • Reduce follow-up questions about why plans moved.
  • Preserve context that may otherwise stay in a private calendar.

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, ask Notis to comment on the related issue when a changed event states a clear reason for rescheduling.
  • 4Choose the Outlook Calendar Event Changes trigger and select where run reports should go.
  • 5Test with one real rescheduled event that includes a reason and review the comment.

Questions about this workflow

Will Notis infer a reason if the event does not provide one?

No. Ask it to comment only when a reason is stated, and to avoid inventing an explanation.

How should the issue be identified?

Put a Jira key or other reliable reference in the event details and tell Notis how to use it.

Does the workflow cover cancelled meetings?

The trigger includes deleted calendar events. Describe separately whether a cancellation with no stated reason should be recorded.

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.

TriggerScheduled

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

ActionInstant

New Contact Added

Triggered when a new contact is added in the Outlook contacts.

TriggerInstant

Add Watcher to Issue

Adds a user to an issue's watcher list by account id.

ActionInstant

Calendar Event Changes

Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.

TriggerInstant

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

ActionInstant

New Calendar Event

Triggered when a new calendar event is created in the Outlook calendar.

TriggerInstant

Bulk Create Issues

Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

ActionInstant

New Outlook Message

Triggered when a new message is received in the Outlook mailbox.

TriggerInstant

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

ActionInstant

New Sent Message

Triggered when a new message is sent from the Outlook mailbox.

TriggerInstant

Link Issues

Links two jira issues using a specified link type with optional comment.

ActionInstant

Create Project

Creates a new jira project with required lead, template, and type configuration.

ActionInstant

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.