Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[feature]: Telegram integration

Open
  • Is something wrong?
#10,013 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Indira-kumar is already working on this.

Since Oct 17, 2026.

  • #10076 by @Indira-kumar — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Domain
api, backend

Research direction

The issue names no files or tests. Start with the existing Slack integration, which the request uses as its model, to see how chat events, commands and user linking are wired. Done would mean the three described behaviours work: event posts to a mapped chat, a command creates a work item, and each Telegram user is linked to their Plane account. Agreeing the design with maintainers comes first.

Written by the indexing model from the issue text.

Description

Is there an existing issue for this?
  • I have searched the existing issues
Summary

Add a native Telegram integration, along the lines of the existing Slack integration. A workspace admin connects a Telegram bot and maps Telegram groups (or forum topics) to Plane projects. The integration then:

  1. Posts work item events to the mapped chat: created, state changed, assigned, commented, and @mentions of the linked user.
  2. Lets members create a work item from a chat message, for example with /plane create <title> or by replying to a message with a command, the same way Slack messages can become work items today.
  3. Links each Telegram user to their Plane account, so actions run with that user's own permissions instead of one shared token.
Why should this be worked on?

Slack is the only chat integration today. Many teams run their day-to-day work in Telegram groups and don't use Slack at all, so for them Plane updates stay inside the app or in email.

The demand is already visible in the community. People have built at least eight separate Plane and Telegram bridges, for example mdportnov/plane-telegram-bot (shared in discussion #7069), csmplay/plane-telegram-webhooks, andreferi3/plane-webhooks, temamint/Plane-Notifications, and the mguptahub/plane-telegram Docker image (about 3K pulls). Each one reimplements the same pieces: webhook signature checks, mapping Plane users to Telegram users, and mapping chats to projects. Several stopped after a few commits. A first-party integration would replace these one-person projects with something maintained and bring Telegram to parity with Slack.

Related requests for other chat platforms: #6001 (Mattermost) and #3416 (Rocket.Chat).

Dominant language
TypeScript
Stars
60.7k
Forks
6k
Avg merge
1d 9h
Merged PRs (30d)
56

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from makeplane/plane

All issues in makeplane/plane

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.