Retrieve system context for deployment status changes
Make deployment status transitions easier to interpret without switching tools.
Trigger
New Deployment Status Created
Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions such as pending, in_progress, success, failure, error, inactive, and queued. The payload includes the status state, creator, environment, description, timestamps, and relevant URLs.
Action
Retrieve System Info
Tool to retrieve signpath system information including product, api version, environment details, and ui base url. use after authentication to fetch the current system metadata.
Why this helps
A deployment status update can demand context from several systems at once.
- Centralizes useful context
- Supports quick triage
Setup
Build it in a few focused steps.
- 1Connect GitHub and SignPath to Notis once.
- 2Create a new portal automation.
- 3Ask Notis to retrieve SignPath system information when a GitHub deployment status is created, select the status trigger and a report channel.
- 4Post a test deployment status and review the run.
Questions about this workflow
Can I receive reports in chat?
Yes. Choose the Notis channel where you want run reports when creating the automation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Signpath. A trigger fires from one place; an action lands in another.
GitHub triggers
Signpath actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Certificates
Tool to retrieve the list of certificates for an organization.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Projects
Tool to list all projects for an organization. use after confirming the organization id to retrieve and paginate project records.
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.
Retrieve Signing Policy Details
Tool to retrieve details about signing policies for the current organization. use when needing to list available signing policies prior to selecting one.
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.
Retrieve System Info
Tool to retrieve signpath system information including product, api version, environment details, and ui base url. use after authentication to fetch the current system metadata.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
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.
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.
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.
Connect any two apps with Notis in the middle.
GitHub and Signpath, 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 Signpath.