Keep deployment context attached to delivery work
Reflect meaningful deployment changes without asking someone to manually update a task.
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
Update Task
Tool to update a task in a project. use after confirming the project and task ids.
Why this helps
Environment and commit changes can make a task misleading during launch or rollback work.
- Keeps deployment details current
- Reduces launch coordination overhead
- Creates a clearer operational history
Setup
Build it in a few focused steps.
- 1Connect GitHub and Bugherd to Notis once through the portal.
- 2Create the automation in the portal or ask Notis in plain language.
- 3Tell Notis: “When a GitHub deployment changes, update the related Bugherd task with the changed fields, current environment, ref, SHA, and deployment link.”
- 4Select GitHub Deployment State Changed, choose a report channel, and test with one deployment update.
Questions about this workflow
Which deployment changes matter most?
Common choices are environment, ref, SHA, description, and production-environment status.
Can this be limited to production?
Yes. Scope the GitHub trigger or specify production-only behavior in the prompt.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Bugherd. A trigger fires from one place; an action lands in another.
GitHub triggers
Bugherd actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Guest to Project
Tool to add a guest (client) to a project. use when you want to add an existing client by id or invite a new client by email.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Member to Project
Tool to add a member to a project in bugherd. use when you need to add an existing user to a specific project.
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.
Create Attachment
Tool to add a new attachment to a task using an existing url. use when you have project and task ids and the external file url ready.
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.
Create Column
Tool to create a new column in a project. use when you need to add a custom workflow column after identifying the project id.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create Comment
Tool to add a new comment to a task. use when you need to record discussion or feedback on an existing task.
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 Project
Tool to create a new project. use when you need to initialize a project after gathering its name and url. example: "create a new project named 'my website' with url 'http://www.example.com'."
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 Task
Tool to add a new task in a project. use when you have the project id and full task details ready.
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 Webhook
Tool to create a new webhook for real-time event notifications. use when you need to configure a callback endpoint for task or comment events. example: "create a webhook for 'task create' events to be sent to 'https://example.com/webhook'."
Connect any two apps with Notis in the middle.
GitHub and Bugherd, 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 Bugherd.