See Dromo upload context alongside job changes
When a job moves or finishes, keep potentially relevant Dromo upload information close to the status update.
Trigger
Workflow Job State Changed
Triggers when the status, conclusion, timestamps, runner assignment, or step details of a specific GitHub Actions workflow job change between polls. The payload includes the full current job state, a list of which fields changed, and the previous status/conclusion values for easy comparison.
Action
List Uploads
Tool to retrieve a list of all uploads stored by dromo for your organization. use when you need to paginate or filter uploads.
Why this helps
Investigating an individual job can involve bouncing between CI details and import records without a clear shared thread.
- Bring an existing Dromo upload list into the job-change report.
- Reduce app switching during job review.
- Avoid asserting a job-to-upload connection without matching details.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Dromo once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Describe in one instruction how to retrieve Dromo uploads and summarize relevant context with the changed job details.
- 4Pick the GitHub Workflow Job State Changed trigger and choose where run reports should go.
- 5Test with one real job state change and check the summary against the source data.
Questions about this workflow
Can this upload job output to Dromo?
No. This workflow uses List Uploads, which retrieves existing Dromo uploads. It does not transfer job files.
What makes an upload relevant to a job?
The automation can compare available details such as names or other shared context if present. A direct linkage is not specified by the available events and action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Dromo. A trigger fires from one place; an action lands in another.
GitHub triggers
Dromo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List Uploads
Tool to retrieve a list of all uploads stored by dromo for your organization. use when you need to paginate or filter uploads.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Upload File To Headless Import
Tool to upload a file to a headless import. use after obtaining a signed upload url from dromo. performs an http put of raw bytes to the provided signed url.
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 Dromo, 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 Dromo.