Send GitHub issue state changes through Svix
Publish tracked GitHub issue changes into Svix so priority, ownership, and closure signals reach the next workflow automatically.
Trigger
Issue State / Properties Changed
Triggers when a specific GitHub issue changes any of its tracked properties. Monitored properties: state (open/closed), state_reason, title, body, assignees, labels, milestone, lock status, active_lock_reason, comment count, and closed_at timestamp. When a change is detected, the payload includes the full current issue details, the list of changed field names, and their previous values.
Action
Create Message
Tool to create a new message for a specific application in svix. use after confirming app id and event details.
Why this helps
A changed issue can silently alter a plan, leaving follow-up dependent on someone noticing the update.
- Turn issue movement into an explicit signal instead of a hidden change in a queue.
- Keep priorities and ownership changes visible.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Svix to Notis in the portal if they are not connected already.
- 2Ask Notis for your portal link, then open Automations and choose New Automation.
- 3Name the automation and write one plain-language instruction: "Svix project events"
- 4Select the GitHub trigger, choose the channel for run reports, and click Create.
- 5Test it with one real example and confirm the Svix result in your report channel.
Questions about this workflow
Reduce the cognitive load of checking every issue.
Can it react to label changes?
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Svix. A trigger fires from one place; an action lands in another.
GitHub triggers
Svix actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Application
Tool to create a new svix application. use when you need to register an application with specific settings.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Svix Application
Tool to delete an application by its id. use when you need to permanently remove a svix application after confirming its id.
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.
Get Application
Tool to retrieve details of a specific svix application by its id. use when you need application metadata after authenticating with svix.
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.
List Applications
Tool to list all applications. use when you need to retrieve or paginate through your svix applications.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Update Svix Application
Tool to update an existing svix application by id. use when you need to modify properties like name, rate limit, uid, or metadata. call after confirming the correct app id.
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.
Get Attempt Details
Tool to retrieve details of a specific message attempt. use after confirming app id, msg id, and attempt id.
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.
List Message Attempts
Tool to list all delivery attempts for a specific message. use after confirming message id to debug attempts.
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 Endpoint
Tool to create a new svix webhook endpoint. use after obtaining the app id to register your webhook receiver url.
Connect any two apps with Notis in the middle.
GitHub and Svix, 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 Svix.