Check GitHub assignee eligibility from Habitica triage
Catch an ownership problem before it becomes another unfinished follow-up.
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 task can look handed off even when the proposed owner cannot receive it.
- Prevents failed handoffs
- Keeps triage decisive
Setup
Build it in a few focused steps.
- 1Connect Habitica and GitHub to Notis once.
- 2Create a new automation in the portal or ask Notis to make one.
- 3Describe checking whether the intended GitHub user can be assigned during triage.
- 4Select the webhook trigger and report channel.
- 5Test it with one known assignable user.
Questions about this workflow
Does it assign the issue?
This workflow checks eligibility so the next assignment decision is informed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Habitica to GitHub. A trigger fires from one place; an action lands in another.
Habitica 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 Habitica and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.