Check Assignment Eligibility from Telegram Instantly

You want to assign someone to an issue but aren't sure if they have push access. Type a quick message in Telegram and Notis tells you if they're eligible. No GitHub context-switch needed.

Trigger

New Message Received

Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.

GitHub logo

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

Uncertainty about permissions causes duplicate work and confusion. Neurodivergent founders need quick verification to avoid assigning work to people who can't do it.

  • Verify assignment eligibility in seconds from Telegram
  • No need to check GitHub settings manually
  • Prevent assigning work to people without push access
  • Reduces frustration from invalid assignments

Setup

Build it in a few focused steps.

  • 1Connect Telegram and GitHub to Notis.
  • 2Create an automation with the prompt: 'When I send a Telegram message asking if someone can be assigned to an issue, check their permission level and tell me yes or no.'
  • 3Select Telegram (New Message) as the trigger.
  • 4Test by sending a message like 'Can @alice be assigned to this repo?' and see the verification result.

Questions about this workflow

What permission level is required to assign someone?

Push access or higher. Notis will tell you their current level (admin, maintain, write, read, or none).

Can I check multiple people at once?

List them in one message: 'Can @alice, @bob, and @carol be assigned?' and Notis checks all three.

What if someone should be eligible but isn't?

Ask Notis to add them as a collaborator first, then try the assignment.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Telegram to GitHub. A trigger fires from one place; an action lands in another.

Telegram logo

Telegram triggers

GitHub logo

GitHub actions

New Message Received

Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.

TriggerInstant

Accept a repository invitation

Accepts a pending repository invitation that has been issued to the authenticated user.

ActionInstant

New Channel Post

Triggered when a new post is published to a channel where your bot is an administrator.

TriggerInstant

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.

ActionInstant

Callback Query Received

Triggered when a user taps an inline keyboard button attached to one of your bot's messages.

TriggerInstant

List stargazers

Deprecated: lists users who have starred a repository; use `list stargazers` instead.

ActionInstant

Message Edited

Triggered when a message in a chat your bot can see is edited by its sender.

TriggerInstant

Star a repository for the authenticated user

Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.

ActionInstant

New Chat Member

Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.

TriggerInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

Connect any two apps with Notis in the middle.

Not just Telegram and GitHub. Any combination from 985+ 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.