Organize GitHub issues with Landbot feedback
Make patterns in customer conversations easier to see and act on.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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 is collected, but labeling issues consistently takes time and gets skipped during busy weeks.
- Creates a dependable feedback taxonomy
- Makes related issues easier to find
- Turns review time into a short automated routine
Setup
Build it in a few focused steps.
- 1Connect Landbot and GitHub to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to create it conversationally.
- 3Use one instruction: review new Landbot feedback and add the most relevant labels to matching GitHub issues.
- 4Pick a recurring schedule and choose the channel for run reports.
- 5Test it with one recent feedback item.
Questions about this workflow
Can labels be created if they do not exist?
Yes. GitHub creates labels supplied by the action when they are missing.
How often can this run?
Choose a recurring schedule that fits your review rhythm, such as daily or weekly.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Landbot to GitHub. A trigger fires from one place; an action lands in another.
Landbot 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 Landbot 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.