Close the loop between release notes and pull requests
A bookmarked launch detail should tell you whether the underlying work is actually done.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Check if pull request merged
Checks if a specified github pull request has been merged, indicated by a 204 http status (merged) or 404 (not merged/found).
Why this helps
Release planning gets out of sync when a bookmarked PR reference is assumed complete without checking GitHub.
- Reduces uncertain release status
- Prevents premature announcements
- Makes follow-up explicit
Setup
Build it in a few focused steps.
- 1Connect Raindrop.io and GitHub to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to create it from chat.
- 3Use this instruction: When a release-related Raindrop webhook arrives, check whether the referenced GitHub pull request has merged and report the result.
- 4Pick an incoming webhook trigger, choose the run-report channel, and test with one real release note.
Questions about this workflow
What happens if the PR is not merged?
Notis reports the outstanding state so you can decide the next follow-up.
Can it check PR links?
Yes, include the link or enough identifying context in the incoming Raindrop signal.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Raindrop.io to GitHub. A trigger fires from one place; an action lands in another.
Raindrop.io triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Raindrop.io and GitHub. Any 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.