Confirm GitHub user assignability from Landbot
Know whether the person named in a request can actually own the next step.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Check if a user can be assigned
Verifies if a github user can be assigned to issues in a repository; assignability is confirmed by an http 204 (no content) response, resulting in an empty 'data' field in the response.
Why this helps
A person is selected during intake, but repository rules prevent them from taking ownership later.
- Avoids invalid ownership assumptions
- Reduces failed routing attempts
- Gives founders a clear exception to resolve
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: when Landbot identifies a proposed GitHub owner, check whether that user can be assigned in the specified repository.
- 4Pick an incoming webhook trigger and choose a channel for run reports.
- 5Test with one intake and proposed owner.
Questions about this workflow
Does the person need to be a collaborator?
GitHub determines assignability for the repository; Notis reports the result returned by GitHub.
Can this check happen before issue creation?
It can verify repository-level assignability for the proposed user before the rest of your process continues.
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
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.
Landbot 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.