Avoid dead-end assignments from Listclean follow-up
Check ownership fit before a task lands in the wrong place.
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 to an issue
Checks if a specified github user can be assigned to a given issue within a repository.
Why this helps
A proposed owner may not be assignable, creating another round of manual correction.
- Prevents invalid assignment attempts
- Makes follow-up routing more reliable
- Reduces back-and-forth during busy weeks
Setup
Build it in a few focused steps.
- 1Connect Listclean and GitHub to Notis once through the portal.
- 2Create the automation or ask Notis to set it up in plain language.
- 3Use this instruction: When Listclean sends a contact for GitHub follow-up, check whether the specified user can be assigned in the repository and report the result.
- 4Select an incoming webhook trigger, choose the report channel, and test with one real contact.
Questions about this workflow
Does this assign the user?
No. It only checks whether the user can be assigned.
Why check before assigning?
It lets you resolve access or repository issues before creating a failed handoff.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Listclean to GitHub. A trigger fires from one place; an action lands in another.
Listclean 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 Listclean 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.