Keep onboarding context beside the setup work
Give the team a shared place to find the setup notes that matter when someone joins the group.
Trigger
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
Action
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
Why this helps
Onboarding details shared at the moment someone joins can be hard for the team to recover later.
- Keep agreed setup notes beside an existing onboarding issue.
- Reduce repeated questions about how to get started.
- Help the team revisit onboarding context after the welcome conversation.
Setup
Build it in a few focused steps.
- 1Connect Telegram and Bitbucket to Notis once in the portal.
- 2Create the automation in the portal or ask Notis conversationally.
- 3Write one instruction describing what useful onboarding context to add and which existing issue to comment on.
- 4Choose New Chat Member as the trigger and select a channel for run reports.
- 5Test with one real member join and relevant onboarding context.
Questions about this workflow
Does this create a new issue?
This workflow comments on an existing onboarding issue identified by your instruction.
Will a join event always contain setup notes?
The workflow should only add a comment when there is useful context to record.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Telegram to Bitbucket. A trigger fires from one place; an action lands in another.
Telegram triggers
Bitbucket actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a branch
Creates a new branch in a bitbucket repository from a target commit hash; the branch name must be unique, adhere to bitbucket's naming conventions, and not include the 'refs/heads/' prefix.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create an issue
Creates a new issue in a bitbucket repository, setting the authenticated user as reporter; ensures assignee (if provided) has repository access, and that any specified milestone, version, or component ids exist.
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.
Create an issue comment
Adds a new comment with markdown support to an existing bitbucket issue.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
Create a pull request
Creates a new pull request in a specified bitbucket repository, ensuring the source branch exists and is distinct from the (optional) destination branch.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
Create repository
Creates a new bitbucket 'git' repository in a specified workspace, defaulting to the workspace's oldest project if `project key` is not provided.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Create snippet comment
Posts a new top-level comment or a threaded reply to an existing comment on a specified bitbucket snippet.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
Delete issue
Permanently deletes a specific issue, identified by its `issue id`, from the repository specified by `repo slug` within the given `workspace`.
Delete repository
Permanently deletes a specified bitbucket repository; this action is irreversible and does not affect forks.
Connect any two apps with Notis in the middle.
Telegram and Bitbucket, 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 Bitbucket.