Move a GitHub workflow artifact into a Dromo import
Turn a new workflow artifact into an import handoff, so build outputs can reach Dromo without a manual download and upload.
Trigger
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.
Action
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.
Why this helps
Build outputs can be easy to overlook when the next step is manually finding, downloading, and uploading an artifact.
- Reduce manual file handoffs after a workflow creates an artifact.
- Keep artifact context with the import request.
- Avoid claiming an upload succeeded unless Dromo provides the required signed URL and the artifact bytes are accessible.
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 use the new artifact for a Dromo headless import, provided its signed upload URL and raw bytes are available.
- 4Pick the GitHub New Workflow Artifact Created trigger and choose where run reports should go.
- 5Test with one real artifact and confirm Dromo accepts the upload.
Questions about this workflow
Does this trigger create a Dromo import session?
No. The available Dromo action uploads raw bytes to a headless import using a signed upload URL obtained from Dromo. The trigger and action list does not include an event to create an import session or obtain that URL.
What if the artifact bytes or signed URL are unavailable?
The upload cannot be completed with the listed action alone. The automation needs both the raw bytes and a valid Dromo signed upload URL before it can call the upload 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.