Surface delivery risks from calendar changes
Catch schedule risk while there is still time to respond.
Trigger
Calendar Event Changes
Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.
Action
Create an issue
Creates a new issue in a bitbucket repository, setting the authenticated user as reporter; ensures assignee (if provided) has repository access, and that any specified milestone, version, or component ids exist.
Why this helps
A moved dependency or shortened review window is noticed too late to protect delivery.
- Make schedule risk explicit
- Prompt earlier decisions
- Keep mitigation work visible
Setup
Build it in a few focused steps.
- 1Connect Outlook and Bitbucket once in Notis.
- 2Create an automation named Calendar change to risk issue.
- 3Tell Notis to create a risk issue only when an event change reduces available time or moves a dependency, including the suspected impact.
- 4Pick Calendar Event Changes as the trigger and choose a report channel.
- 5Test with one materially shortened timeline.
Questions about this workflow
Can it estimate the risk?
It can summarize the visible schedule impact, while clearly labeling unknowns for human review.
Will minor edits create noise?
Tell Notis to ignore changes that do not affect timing, dependencies, or attendance.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Outlook to Bitbucket. A trigger fires from one place; an action lands in another.
Outlook triggers
Bitbucket actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a branch
Creates a new branch in a bitbucket repository from a target commit hash; the branch name must be unique, adhere to bitbucket's naming conventions, and not include the 'refs/heads/' prefix.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create an issue
Creates a new issue in a bitbucket repository, setting the authenticated user as reporter; ensures assignee (if provided) has repository access, and that any specified milestone, version, or component ids exist.
New Contact Added
Triggered when a new contact is added in the Outlook contacts.
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
Calendar Event Changes
Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.
Create a pull request
Creates a new pull request in a specified bitbucket repository, ensuring the source branch exists and is distinct from the (optional) destination branch.
New Calendar Event
Triggered when a new calendar event is created in the Outlook calendar.
Create repository
Creates a new bitbucket 'git' repository in a specified workspace, defaulting to the workspace's oldest project if `project key` is not provided.
New Outlook Message
Triggered when a new message is received in the Outlook mailbox.
Create snippet comment
Posts a new top-level comment or a threaded reply to an existing comment on a specified bitbucket snippet.
New Sent Message
Triggered when a new message is sent from the Outlook mailbox.
Delete issue
Permanently deletes a specific issue, identified by its `issue id`, from the repository specified by `repo slug` within the given `workspace`.
Delete repository
Permanently deletes a specified bitbucket repository; this action is irreversible and does not affect forks.
Connect any two apps with Notis in the middle.
Outlook and Bitbucket, 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 Bitbucket.