Put a beach plan review in the right hands
When a check needs a human decision, route the existing planning issue to the owner you name in your instruction.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
A concern about weather or tides can go unowned when everyone assumes someone else will review it.
- Give a conditions review a clear owner.
- Route only the issue that needs attention based on criteria you provide.
- Start the check from an HTTP request in an existing process.
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 or location, repository and issue, review threshold, and GitHub username to assign when the threshold is met.
- 4Choose a webhook trigger, select where run reports should go, then test with one real beach example.
Questions about this workflow
What starts the check?
An HTTP request to the Notis webhook starts it. Beach Day API does not provide its own trigger event.
Who gets assigned?
Name the GitHub username in the instruction. The workflow uses that person when the returned conditions meet your review threshold.
What if the conditions do not meet the threshold?
State in the instruction that the issue should remain unchanged unless the threshold is met. Test both a qualifying and non-qualifying example.
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.