Give support escalations a visible GitHub owner
When a customer problem is worth escalating, ownership should not wait for another handoff.
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
Support escalations are saved for engineering but lose urgency while waiting for manual issue routing.
- Makes escalations actionable
- Reduces handoff delay
- Creates a clear next owner
Setup
Build it in a few focused steps.
- 1Connect Raindrop.io and GitHub to Notis once through the portal.
- 2Create the automation in Automations -> New Automation, or ask Notis conversationally.
- 3Describe the outcome: When a support escalation arrives by Raindrop webhook, find the matching GitHub issue and assign it to the owner named by the escalation rule.
- 4Choose an incoming webhook trigger, select the run-report channel, and test with one real escalation.
Questions about this workflow
Can it handle priority information?
It can use priority context to identify the relevant issue or owner, while the GitHub action assigns the issue.
What if the issue is already assigned?
Tell Notis whether to preserve current ownership or report the conflict.
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
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.
Raindrop.io 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.