Catch tide and beach rule changes in your plan
Keep tide timing and local rules in view by turning the conditions you care about into a review label on the planning issue.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Tide timing and beach rules are easy to overlook when planning details live in separate places.
- Bring tide and rule checks into the issue where the plan is tracked.
- Surface only the cases that meet the criteria you set.
- Reduce repeated checks across browser tabs and notes.
Setup
Build it in a few focused steps.
- 1Connect Beach Day API and GitHub once in the Notis portal.
- 2Create an automation in Automations > New Automation and name it.
- 3In one instruction, specify the beach, repository and issue, the tide or rule criteria to review, and the label to add when they match.
- 4Choose a recurring schedule, select where run reports should go, then test with one real beach example.
Questions about this workflow
Can the workflow tell me which tide time is best?
It can examine available tide predictions against criteria you provide. Name the relevant timing window and what should trigger a review.
Does it create a GitHub issue?
No. This workflow adds a label to an existing issue. Specify the repository and issue to update.
Can it check rules for any country?
Beach Day API provides country coverage data. Name the location and have the instruction report when the API does not return the needed coverage or rule information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Beach Day API to GitHub. A trigger fires from one place; an action lands in another.
Beach Day API triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
Beach Day API and GitHub, 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 GitHub.