Connect Telegram and Jira to power automations.

Trigger from one app, act on another, with a thinking brain in the middle. Build it in plain English. Approve from your phone.

When this happens · Trigger

Do this · Action

Build an automation Browse templates

Popular workflows

Most used workflows for Telegram + Jira

Details

Capture Ideas Instantly: Message to Jira Task

Turn quick Telegram thoughts into tracked Jira tasks without context-switching.

Details

Group Discussions to Jira Backlog: Bulk Task Creation

Turn Telegram group threads into multiple Jira tasks, perfect for converting brainstorms into actionable work.

Details

Channel Announcements to Tracked Jira Issues

Turn Telegram channel posts into Jira tasks, ensuring public announcements become tracked work.

Details

One-Tap Approval: Telegram Button to Jira Workflow

Approve or advance Jira issues with a single button tap in Telegram—no context-switching needed.

Details

Instant Task Assignment: Telegram Message to Jira Owner

Create and assign a Jira task to a team member in one Telegram message.

Details

Evidence and Context: Telegram Attachments to Jira Issues

Attach files, screenshots, and links from Telegram messages to Jira issues automatically.

Details

Team Visibility: Add Watchers From Telegram Mentions

Automatically add Telegram users as Jira watchers to keep stakeholders updated.

Details

Mark Priority Instantly: Telegram to Jira Field Update

Flag urgent work with Telegram keywords—Notis updates Jira priority automatically.

Details

Connected Work: Link Related Jira Issues From Telegram

Mention related work in Telegram, and Notis links those issues automatically.

Supported Triggers and Actions

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

Telegram triggers

Jira 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

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

New Channel Post

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

TriggerInstant

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

ActionInstant

Callback Query Received

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

TriggerInstant

Add Watcher to Issue

Adds a user to an issue's watcher list by account id.

ActionInstant

Message Edited

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

TriggerInstant

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

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

Bulk Create Issues

Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

ActionInstant

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

ActionInstant

Link Issues

Links two jira issues using a specified link type with optional comment.

ActionInstant

Create Project

Creates a new jira project with required lead, template, and type configuration.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.