Route Beehiiv reader feedback into GitHub issue labels
Keep newsletter feedback close to the work it informs. Send a feedback event to Notis and add useful labels to the matching GitHub issue.
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
Reader feedback can sit in a separate inbox while the related product issue stays untagged and hard to find.
- Make reader feedback easier to find alongside related product work.
- Apply consistent labels based on the feedback context.
- Reduce manual handoff from newsletter operations to engineering.
Setup
Build it in a few focused steps.
- 1Connect Beehiiv and GitHub once in the Notis portal.
- 2Create an automation in the portal or tell Notis in plain language from any channel.
- 3In one instruction, explain how to identify the existing GitHub issue and which labels fit the feedback.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real feedback event and confirm the intended issue receives the right labels.
Questions about this workflow
Does Beehiiv provide a trigger event for this workflow?
No Beehiiv trigger events are listed here. Start the automation with a Notis webhook and send it a request when your feedback process has a relevant event.
Does this create a GitHub issue?
No. The available action adds labels to an existing issue. Include enough information in the webhook request for Notis to identify that issue.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Beehiiv to GitHub. A trigger fires from one place; an action lands in another.
Beehiiv 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.
Beehiiv 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.