Skip to content
Notis

Check Dromo uploads when a branch changes

A branch update can be a useful cue to check existing Dromo imports alongside the latest repository activity.

Trigger

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.

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

Branch progress and data import activity are easy to track in separate places, creating extra follow-up work.

  • Prompt an upload check when a branch changes.
  • Keep potential import context alongside branch activity.
  • Avoid treating a branch and upload as related without evidence.

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 report details relevant to the branch change.
  • 4Pick the GitHub Branch Changed trigger and choose where run reports should go.
  • 5Test with a real branch change and inspect the report.

Questions about this workflow

What types of branch changes are covered?

The trigger monitors new commits and changes to branch protection status or settings.

Can the report compare upload data to branch history?

It can compare only details present in the trigger payload and Dromo upload results. The listed Dromo action does not provide GitHub history.

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.