Update an existing UptimeRobot monitor from a GitHub task
When a monitor-maintenance issue is assigned to you, Notis can apply the requested edit to the existing UptimeRobot monitor identified in the issue.
Trigger
New Issue Assigned to Me
Triggers when a new issue is assigned to the authenticated user. Fires an event for each GitHub issue that is newly assigned to the authenticated user. Pull requests are automatically excluded -- only true issues are emitted. Issues can optionally be filtered by labels and state. The payload includes the issue number, title, body, state, labels, assignees, creator, repository details, and timestamps.
Action
Edit Monitor
Tool to edit an existing monitor. use after confirming the monitor id exists.
Why this helps
Small monitor-setting changes can sit in the task queue while someone switches tools to locate the right monitor.
- Apply a specific monitor change when its follow-up issue becomes yours.
- Avoid editing a different monitor by requiring the existing monitor ID in the request.
Setup
Build it in a few focused steps.
- 1Connect GitHub and UptimeRobot to Notis once in the portal.
- 2Create the automation in the portal or ask Notis for it in plain language.
- 3Tell Notis to edit only an existing monitor whose ID and requested change are explicit in the assigned issue; skip ambiguous requests.
- 4Select GitHub New Issue Assigned to Me and choose where run reports should go.
- 5Test with one assigned issue naming an existing monitor ID and a supported change.
Questions about this workflow
Will it create a monitor if the ID is missing?
No. This workflow is for editing an existing monitor and should run only when the issue provides the monitor ID and a clear requested change.
Can it edit any kind of UptimeRobot setting?
The request lists the Edit Monitor action but does not enumerate its editable fields. Keep the instruction to changes supported by the connected action and have Notis report any unsupported request.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Uptimerobot. A trigger fires from one place; an action lands in another.
GitHub triggers
Uptimerobot actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Monitor
Tool to create a new monitor. use when you need to start monitoring a url or service; call after obtaining a valid api key.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Monitor
Tool to delete a monitor. use when you need to remove an existing monitor by its id; use after confirming the monitor id.
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.
Edit Maintenance Window
Tool to edit an existing maintenance window. use when you need to update its name, timing, recurrence, or duration after confirming the window id.
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.
Edit Monitor
Tool to edit an existing monitor. use after confirming the monitor id exists.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Edit Public Status Page
Tool to edit an existing public status page. use after confirming the page id. updates friendly name, monitor set, domain, and status options in one call.
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 Account Details
Tool to retrieve account details. use after authenticating with a valid api key to fetch account metrics.
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 Maintenance Windows
Tool to retrieve maintenance windows. use after confirming a valid api key.
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.
Get Monitor Authentication Type
Tool to get authentication type for specified monitors. use after providing monitor ids to check http basic auth status.
Connect any two apps with Notis in the middle.
GitHub and Uptimerobot, 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 Uptimerobot.