Start a post-deployment checklist from GitHub
When a deployment reaches success in your configured production environment, Notis can start the matching Process Street checklist run for the follow-up work.
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
Create Workflow Run
This tool creates a new workflow run from a specified workflow template. it is one of the most fundamental operations in process street, allowing users to initiate a new instance of a workflow. the tool requires a workflow template id and optionally allows setting a custom name, due date, and whether to enable a share link.
Why this helps
After a release goes live, operational checks can slip while attention shifts to the next task.
- Start a repeatable follow-up checklist only after the deployment reports success.
- Keep production release routines visible in the process tool your team already uses.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Process Street to Notis once in the portal.
- 2Create the automation in the portal or ask Notis for it in plain language.
- 3Tell Notis which existing Process Street post-deployment workflow template to start, and to proceed only when GitHub reports success for the configured production environment.
- 4Select GitHub New Deployment Status Created and choose where run reports should go.
- 5Test against one deployment status event for a non-production environment or controlled test deployment.
Questions about this workflow
Does this start a checklist for failed or in-progress deployments?
No. The instruction requires a success status and the configured production environment before creating the Process Street run.
Does it create a new Process Street workflow template?
No. It starts a run from an existing template identified in the instruction; it does not create a template.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Process street. A trigger fires from one place; an action lands in another.
GitHub triggers
Process street actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Complete a workflow run
This tool marks an entire workflow run as completed in process street. it updates the workflow run's status to 'completed', distinguishing it from process street complete task which completes individual tasks.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Workflow Run
This tool creates a new workflow run from a specified workflow template. it is one of the most fundamental operations in process street, allowing users to initiate a new instance of a workflow. the tool requires a workflow template id and optionally allows setting a custom name, due date, and whether to enable a share link.
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.
Find Data Set Rows
This tool allows you to search for records within a data set based on form fields. it's useful for retrieving specific records from a data set when you need to find matching entries based on certain criteria.
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 Workflows
This tool retrieves a list of all workflows available in the process street account. it is a fundamental action that allows users to view and access all their workflows, which is essential for other operations that require workflow ids. this action is important because it provides the foundation for other actions that require workflow ids as input parameters, such as creating workflow runs or managing workflow-specific tasks, thereby enabling better workflow management and automation.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Undelete Workflow Run
This tool allows you to restore a previously deleted workflow run in process street. it uses the put /v1.1/workflow-runs/{workflowrunid}/undelete endpoint to recover a workflow run within a valid recovery period. it complements the existing process street delete workflow run action by providing a data recovery option to correct deletion mistakes.
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 Process street, 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 Process street.