Align your team on deployment status changes
When a deployment's status changes in GitHub, Notis blocks time on your team's calendars for a quick sync so everyone knows the current state and next steps.
Trigger
GitHub Deployment State Changed
Triggers when a specific GitHub deployment's fields change. Monitors the following aspects of a single deployment: - ``environment`` -- the target environment name - ``original_environment`` -- the original environment name before normalization - ``description`` -- the human-readable deployment description - ``task`` -- the deployment task name - ``sha`` -- the commit SHA being deployed - ``ref`` -- the branch, tag, or SHA reference being deployed - ``updated_at`` -- the last-updated timestamp - ``transient_environment`` -- whether the environment is temporary - ``production_environment`` -- whether this is a production deployment When any of these fields change, an event is emitted containing the full current deployment details and a list of which fields changed.
Action
Create Event
Creates an event on a google calendar, needing rfc3339 utc start/end times (end after start) and write access to the calendar. by default, adds the organizer as an attendee unless exclude organizer is set to true.
Why this helps
A deployment fails. You see the notification. But status updates get shared via Slack messages across different channels. Some people don't see them. Confusion about whether we're rolling back, retrying, or investigating. Everyone has different mental models of what's happening. You waste time in DMs clarifying instead of having one team moment.
- Ensure your whole team has the same understanding of deployment status by holding a quick sync when it changes
- Reduce confusion and friction by having one coordinated conversation instead of scattered Slack messages
- Enable fast decision-making on rollbacks or retries by getting everyone on the same page quickly
Setup
Build it in a few focused steps.
- 1Connect GitHub and Google Calendar to Notis
- 2Ask Notis: 'When a deployment status changes, block time on my team's calendar for a quick sync' or set it up in Automations
- 3Specify your team members or Slack channel to include in the meeting
- 4Choose your notification channel for alerts
- 5Change a deployment status and confirm the calendar event appears and notifications go out
Questions about this workflow
Does this interrupt people or just block time?
It can do either. Tell Notis to auto-book or just reserve time for you to manually schedule if you prefer less interruption.
Should I include everyone or just the incident responders?
You can configure it either way. A quick sync with the full team often reduces confusion faster than async updates.
What if it's not urgent?
Tell Notis to batch non-critical status changes into a daily review meeting instead of blocking time for each one.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Google Calendar. A trigger fires from one place; an action lands in another.
GitHub triggers
Google Calendar actions
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Insert Calendar into List
Inserts an existing calendar into the user's calendar list.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Update Calendar List Entry
Updates an existing entry on the user\'s calendar list.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Delete Calendar
Deletes a secondary calendar. use calendars.clear for clearing all events on primary calendars.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Update Calendar
Updates metadata for a calendar.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Clear Calendar
Clears a primary calendar. this operation deletes all events associated with the primary calendar of an account.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Create Event
Creates an event on a google calendar, needing rfc3339 utc start/end times (end after start) and write access to the calendar. by default, adds the organizer as an attendee unless exclude organizer is set to true.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Delete event
Deletes a specified event by `event id` from a google calendar (`calendar id`); this action is idempotent and raises a 404 error if the event is not found.
Commit Event
Triggered when a new commit is pushed to a repository.
Create a calendar
Creates a new, empty google calendar with the specified title (summary).
Connect any two apps with Notis in the middle.
Not just GitHub and Google Calendar. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Google Calendar.