Connect repository content changes with Dromo uploads
When a monitored file or directory changes, bring a Dromo uploads lookup into the same follow-up report.
Trigger
Repository Content Changed
Triggers when the content of a file or directory in a GitHub repository changes. Monitors a specified path within a repository on a given branch or tag. For a single file, fires ``content_changed`` when the file is modified. For a directory, fires ``content_changed``, ``content_added``, or ``content_removed`` for modified, new, or deleted entries respectively. content.
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
Changes to data or configuration files may affect imports, but checking Dromo requires a separate reminder and search.
- Prompt an upload lookup when monitored repository content changes.
- Keep changed path details together with import information.
- Help spot relevant context without assuming the content itself is uploaded.
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 details relevant to the changed repository content.
- 4Pick the GitHub Repository Content Changed trigger and choose where run reports should go.
- 5Test with a real content change and confirm the report stays grounded in available data.
Questions about this workflow
Does this send the changed file to Dromo?
No. This workflow lists Dromo uploads. The upload action would require raw bytes and a Dromo signed upload URL, and the listed events do not create that URL.
Can it monitor any repository path?
The trigger monitors a specified file or directory on a given branch or tag. The trigger configuration is selected in the automation flow.
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.