Label GitHub issues from new Dropbox specs
A new spec should create momentum, not another thing to remember.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Important product context lands in Dropbox, but GitHub issues remain unmarked and easy to lose in the queue.
- Makes newly documented work visible in the GitHub queue
- Reduces repeated manual triage
- Creates a consistent signal for what needs attention
Setup
Build it in a few focused steps.
- 1Connect Dropbox and GitHub to Notis once through the portal.
- 2Create an automation in Automations -> New Automation, or ask Notis to create it conversationally.
- 3Give Notis one plain-language instruction: when a Dropbox product spec arrives, find the related GitHub issue and add the appropriate label.
- 4Choose the Notis webhook trigger, select a channel for run reports, and test with one real spec.
Questions about this workflow
Does Dropbox need a native trigger?
No. Dropbox sends the event to a Notis webhook, which starts the automation.
How does Notis know which GitHub issue to label?
Your plain-language instruction tells Notis how to identify the related issue from the Dropbox content.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Dropbox to GitHub. A trigger fires from one place; an action lands in another.
Dropbox 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 Dropbox 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.