Turn Bubble feedback into organized GitHub issues
Keep product feedback moving from Bubble into GitHub with labels that make the next step easier to spot.
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
Feedback can land in GitHub without the labels that help you find and prioritize it later.
- Reduce manual issue sorting after feedback arrives.
- Make incoming feedback easier to find by topic.
- Keep the triage decision close to the issue.
Setup
Build it in a few focused steps.
- 1Connect Bubble and GitHub once in the Notis portal.
- 2Create an automation and describe how incoming feedback should be matched to a GitHub issue and labeled.
- 3Choose a Notis webhook trigger and send it from the Bubble workflow that reports feedback.
- 4Choose where run reports should go.
- 5Test with one real feedback example and confirm the intended issue receives the labels.
Questions about this workflow
Does Bubble provide a trigger event for this workflow?
No Bubble trigger event is listed here. Use a Notis webhook and configure Bubble to send the relevant request to it.
Can Notis create a label if it does not exist?
The GitHub action supports labels that do not already exist, so Notis can apply a useful label set to the matched issue.
What should the webhook include?
Include enough context to identify the relevant GitHub issue and understand the feedback. The workflow cannot infer issue details that Bubble does not send.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bubble to GitHub. A trigger fires from one place; an action lands in another.
Bubble 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.
Bubble 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.