Check Ninox databases when a new GitHub issue arrives
A new issue can prompt a quick database check, so you do not have to remember where project context lives.
Trigger
Issue Added Event
Triggered when a new issue is added to the repository.
Action
Get Databases
Tool to retrieve all databases in a specific ninox team. use after confirming the team id is correct.
Why this helps
Issue intake creates a context hunt before you can decide what matters.
- Reduces context switching
- Creates a repeatable issue-intake ritual
Setup
Build it in a few focused steps.
- 1Connect GitHub and Ninox to Notis once.
- 2Create a new automation in the portal.
- 3Ask Notis to retrieve Ninox databases and report relevant context when a new issue arrives.
- 4Select Issue Added Event and choose your run-report channel.
- 5Test with one real low-risk issue.
Questions about this workflow
Does this change my Ninox data?
No. This action retrieves the available databases for context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Ninox. A trigger fires from one place; an action lands in another.
GitHub triggers
Ninox actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Databases
Tool to retrieve all databases in a specific ninox team. use after confirming the team id is correct.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Record
Tool to delete a record from a specified table. use after confirming workspace, database, table, and record ids.
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 Ninox, 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 Ninox.