Check a known droplet with deployment status updates
For deployments you have linked to a known droplet ID, retrieve that droplet's current details whenever a status update arrives.
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 Existing Droplet
Tool to show information about an individual droplet by id. use when you have a droplet id and need detailed status.
Why this helps
Deployment status and server health details live in different tools, making a quick check feel like a scavenger hunt.
- Bring known droplet details into status review
- Keep deployment status and server context together
- Reduce manual lookup for linked resources
Setup
Build it in a few focused steps.
- 1Connect GitHub and DigitalOcean once in the Notis portal.
- 2Create an automation that retrieves the known DigitalOcean droplet details for a deployment status and summarizes the result.
- 3Pick GitHub's New Deployment Status Created trigger for the deployment you monitor.
- 4Choose where run reports go, then test with one real status update.
Questions about this workflow
What does the workflow need to look up the droplet?
It needs the DigitalOcean droplet ID associated with the deployment. Provide that relationship in your instruction if the event does not include it.
Does a deployment status update change the droplet?
No. The action retrieves droplet details and does not modify the droplet.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Digital ocean. A trigger fires from one place; an action lands in another.
GitHub triggers
Digital ocean actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Custom Image
Tool to create a new custom image by providing a url to a linux vm image. use when you need to import a vm image into digitalocean after specifying name, url, distribution, and region.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Database Cluster
Tool to create a new managed database cluster. use when you need to provision a database cluster with name, engine, version, region, size, and number of nodes.
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 New Block Storage Volume
Tool to create a new block storage volume. use when you need to provision persistent block storage after confirming the target region supports volumes. example: "create a 100 gib ext4 backup volume named 'db-backup' in nyc1."
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 New Domain
Tool to create a new domain. use when you have the domain name and optionally an ip address to assign an a record.
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 Domain Record
Tool to create a new dns record for a domain. use after confirming domain exists and record specifics.
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 New Droplet
Tool to create a new droplet. use when you need to provision a vm with name, region, size, and image.
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 New Firewall
Tool to create a new firewall. use when you need to define a firewall name and custom rules (requires at least one inbound and one outbound rule).
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 New Kubernetes Cluster
Tool to create a new kubernetes cluster. use when you have finalized the cluster name, region, version, and at least one node pool. confirm region supports kubernetes clusters before use.
Connect any two apps with Notis in the middle.
GitHub and Digital ocean, 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 Digital ocean.