Tide-station discovery from README changes
Keep marine documentation updates connected to available stations.
Trigger
GitHub Repository README Changed
Triggers when the README file in a specific repository directory changes. Monitors the README in a configurable directory and branch/tag/commit. The payload includes the current README metadata (filename, path, SHA, size, URLs), the previous and current git blob SHAs, and a list of which tracked fields changed.
Action
List All Tide Stations
Tool to list all available tide stations. use when you need a catalog of stations before querying tide data.
Why this helps
A documentation edit can signal a new operating area, yet station research is easy to defer.
- Makes station discovery timely
- Avoids another research thread
Setup
Build it in a few focused steps.
- 1Connect GitHub and Stormglass io to Notis once.
- 2Create an automation in the portal.
- 3Tell Notis to list available tide stations when the monitored marine README changes.
- 4Select GitHub Repository README Changed, choose a channel, and test a README update.
Questions about this workflow
Does this retrieve tides?
It lists the available tide stations so you can identify the relevant monitoring options.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Stormglass io. A trigger fires from one place; an action lands in another.
GitHub triggers
Stormglass io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Elevation for Point
Tool to fetch elevation data for a single geographic point. use when you need bathymetry or topography for a specific latitude/longitude.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List All Tide Stations
Tool to list all available tide stations. use when you need a catalog of stations before querying tide data.
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 solar data for a point
Tool to fetch solar irradiation and sun-position data for a specific coordinate. use after confirming lat/lng, desired parameters, and optional iso-formatted start/end.
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 weather data for a point
Tool to fetch marine and land weather data for a specific coordinate. use after confirming latitude, longitude, and desired parameters.
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 Stormglass io, 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 Stormglass io.