Connect GitHub to Minerstat
When something happens in GitHub, Notis takes the next step in Minerstat. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from GitHub to Minerstat
Check the mining worker after a failed GitHub check
When a monitored GitHub check fails, Notis retrieves the relevant Minerstat worker status so you can quickly separate code problems from infrastructure problems.
Investigate workflow failures with worker activity
When a GitHub Actions workflow changes to a failed conclusion, Notis retrieves the worker activity log to reveal recent offline events and errors.
Verify worker health after a deployment status
When a GitHub deployment status changes, Notis retrieves detailed Minerstat worker data to help confirm that operational infrastructure remains healthy.
Add worker context to code scanning alerts
When GitHub creates a code scanning alert, Notis retrieves recent Minerstat worker activity so security triage has operational context without extra searching.
Check mining workers after a secret scanning alert
When GitHub detects a secret, Notis retrieves detailed Minerstat worker data to help you assess operational exposure quickly.
Add current coin data to new mining issues
When a new GitHub issue is created, Notis retrieves current Minerstat coin data to provide price, difficulty, reward, and network context for mining-related decisions.
Benchmark hardware context for new mining pull requests
When a new GitHub pull request is created, Notis retrieves Minerstat hardware data to support changes involving GPUs, ASICs, power use, or hashrate.
Surface pool options for new deployments
When a GitHub deployment is created, Notis retrieves Minerstat pool data to confirm available pools, supported coins, fees, and payout thresholds.
Add coin context to new build artifacts
When a GitHub Actions artifact is uploaded, Notis retrieves current Minerstat coin data for the related project so build outputs arrive with fresh economic context.
Supported Triggers and Actions
Notis builds workflows that link GitHub to Minerstat. A trigger fires from one place; an action lands in another.
GitHub triggers
Minerstat actions
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.
Get Coins Data
Retrieves mining coin data from minerstat API including hashrates, difficulty, rewards, and prices. Use this tool to get current mining statistics for cryptocurrencies. You can filter results by specific coin tickers (e.g., 'BTC,ETH') or by mining algorithms (e.g., 'SHA-256,Ethash'). Returns data such as network hashrate, difficulty, estimated mining rewards, current price, and trading volume for each coin. Note: `difficulty` and network hashrate fields may be null for some coins; validate their presence before using in calculations.
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.
Get Hardware Data
Retrieve mining hardware data from minerstat including hashrates, power consumption, and specifications. Use this tool to get benchmark data for GPUs and ASIC miners to compare mining performance across different hardware. Filter by type (gpu/asic) or brand to narrow results. Combine both filters together to avoid mixed variants with differing hashrate and power draw values.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Get Pools Data
Retrieve mining pool data from minerstat. Requires an authenticated minerstat connection. Returns a list of mining pools with their supported coins, fees, payout thresholds, and other details. Use to discover pools for a specific coin or explore all available mining pools.
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.
Get Worker Activity
Retrieve activity logs for a specific worker for the last 3 days. Returns online/offline events, errors, and other activity for troubleshooting worker uptime issues or auditing worker behavior. The API key is automatically extracted from the Authorization header.
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.
Get Worker Data
Retrieve detailed real-time data for a specific mining worker. This tool fetches comprehensive information about a worker including: - Current status (online/offline/idle) - Hardware info (GPUs/ASICs with temperatures, fans, power) - Mining info (coin, pool, client software) - Hashrate data (current hashrates for main/dual/CPU mining) - Share statistics (accepted, rejected, stale) - Revenue estimates Use this when you need detailed metrics for a specific worker. The worker name must exactly match a worker configured in the minerstat dashboard. Returns found=False if the worker doesn't exist.
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.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Commit Event
Triggered when a new commit is pushed to a repository.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it trough Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect GitHub and Minerstat
Connect any two apps with Notis in the middle.
Not just GitHub and Minerstat. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Minerstat.