Keep Environment Updates Easy to Illustrate
A deployment change is a natural checkpoint for refreshing the visual details people rely on.
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
Upload Image to ImgBB
Tool to upload an image to ImgBB. Use when you need to host an image and get back its URLs immediately.
Why this helps
Environment changes create hidden documentation and screenshot work that is easy to postpone or lose.
- Supports clearer environment communication
- Reduces documentation drift
- Creates useful checkpoints
Setup
Build it in a few focused steps.
- 1Connect GitHub and ImgBB once through the Notis portal.
- 2Create the automation in the portal or ask Notis to create it by conversation.
- 3Tell Notis to retrieve and validate the ImgBB API key when the monitored deployment changes, then report readiness for updated visuals.
- 4Select the deployment state change trigger, choose a reporting channel, and test with one deployment update.
Questions about this workflow
Which deployment changes matter?
The trigger monitors deployment fields such as environment, ref, description, and task.
Can this upload the updated screenshot?
Use the upload action when you have a specific image to host; this workflow checks access.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Imgbb. A trigger fires from one place; an action lands in another.
GitHub triggers
Imgbb actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get ImgBB API Key
Tool to retrieve and validate the ImgBB API key. Use before making ImgBB API calls to ensure authentication is configured.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Upload Image to ImgBB
Tool to upload an image to ImgBB. Use when you need to host an image and get back its URLs immediately.
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.
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.
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 Imgbb, 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 Imgbb.