Skip to content
Notis

Send a workflow run artifact to Dromo

Get test results, reports, or other run outputs ready for Dromo as soon as a workflow uploads them.

Trigger

New Artifact Added to Workflow Run

Triggers when a new artifact is uploaded to a specific GitHub Actions workflow run. Monitors a single workflow run for newly added artifacts such as build outputs, test results, or coverage reports. Each new artifact detected fires a separate event.

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

Finding a particular run's artifact later adds a manual search step between CI and data import.

  • Respond to artifacts attached to a specific workflow run.
  • Reduce the chance that run output is left unused.
  • Preserve a clear run-to-import handoff when Dromo upload prerequisites are available.

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 upload a newly added run artifact to Dromo when its raw bytes and signed upload URL are available.
  • 4Pick the GitHub New Artifact Added to Workflow Run trigger and choose where run reports should go.
  • 5Test with one real run artifact and confirm the Dromo upload result.

Questions about this workflow

How is this different from watching all workflow artifacts?

This trigger watches for a new artifact on a specific workflow run. The New Workflow Artifact Created trigger monitors newly created artifacts in a repository.

Can the automation obtain the signed upload URL?

No such Dromo action is listed. The signed upload URL must be available from Dromo, along with the raw artifact bytes, before the upload action can run.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

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.

TriggerPolling

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.

TriggerPolling

New Branch Created

Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

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.

TriggerPolling

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.