Keep Sentry release tracking aligned with GitHub
A published GitHub release can become a Sentry release for the projects you configure. Use the tag as the release version and avoid a separate manual release setup step.
Trigger
GitHub Release State Changed
Triggers when a specific GitHub release (identified by tag name) changes. Monitors the release title, body/notes, draft flag, prerelease flag, published timestamp, target branch/commit, and the set of attached assets. The payload includes the full current release details, a list of which fields changed, and the previous values for comparison.
Action
Create release for organization
Creates a new sentry release for an existing organization, associating it with specified projects that must belong to that organization.
Why this helps
Shipping a GitHub release and registering that version in Sentry are separate tasks, so monitoring context can lag behind the code release.
- Create a Sentry release for configured projects when the GitHub release is published.
- Use the GitHub release tag as the Sentry release version for consistent reference.
- Reduce manual duplication between release management and error monitoring setup.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Sentry to Notis once, and identify the Sentry organization and existing projects that should receive releases.
- 2Create an automation in the portal or ask Notis conversationally; instruct it to create a Sentry release only after the monitored GitHub release is published, using its tag as the version.
- 3Select the GitHub release state-changed trigger for the intended tag and choose a channel for run reports.
- 4Test with one real published release and confirm the Sentry release uses the expected version and projects.
Questions about this workflow
Will a draft GitHub release create a Sentry release?
The GitHub trigger also observes draft and other release changes. The Notis instruction should run only after the release is published, not while it remains a draft.
Does this create a Sentry project?
No. The action creates a release for an existing Sentry organization and projects. Specify the projects that should receive the release.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Sentry. A trigger fires from one place; an action lands in another.
GitHub triggers
Sentry actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Access project information
Retrieves detailed information for a sentry project, given its existing organization and project id or slug.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add organization member via email
Invites a new member (or re-invites an existing non-accepted member) to a sentry organization via email, allowing specification of organization and team roles.
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.
Add or remove user email by id
Adds or removes a secondary email for an existing sentry user, determined by whether the email already exists for that user.
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.
Add team member in organization
Adds an existing member of an organization to one of its teams; the member must already belong to the organization, and the team must also belong to that organization.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Add team to project
Grants a sentry team access to a sentry project within the specified sentry organization.
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.
Create dashboard with widgets
Creates a sentry dashboard with widgets for an organization; `organization id or slug` and specified `project` ids must be valid, and `start`/`end` datetimes (if absolute range) must form a logical iso 8601 range.
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.
Create external user for organization
Links a sentry user to an external identity provider's user within a sentry organization; the sentry user must be an organization member, an active integration for the provider must be configured, and `external id` is typically required for the external user.
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 organization alert rule
Creates a sentry metric alert rule for an organization, mandating a 'critical' trigger, typically for a single project, where actions may require sentry integrations.
Connect any two apps with Notis in the middle.
GitHub and Sentry, 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 Sentry.