Connect Codemagic to Telegram

When something happens in Codemagic, Notis takes the next step in Telegram. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Codemagic to Telegram

View example

Send Codemagic build failures to Telegram

Check Codemagic on a schedule and send Telegram a concise alert when a build fails, with the app, build identifier, and available failure details.

View example

Deliver Codemagic release artifacts to Telegram

Check Codemagic for newly available release artifacts and send selected files to a Telegram chat for review or handoff.

View example

Ask Telegram for a release review decision

When a scheduled Codemagic check finds a candidate release build, post a Telegram poll asking the team whether it is ready for review or needs another pass.

View example

Refresh a Telegram build status message

On a schedule, check Codemagic and update a designated Telegram status message with the latest available build or pipeline state.

View example

Share Codemagic build screenshots in Telegram

Check Codemagic for newly available build screenshots or preview images and send them to Telegram for visual review.

View example

Send Codemagic pipeline updates to Telegram

Start a Notis webhook from a Codemagic pipeline step and send the supplied build update to a Telegram chat as a concise message.

View example

Hand off Codemagic artifacts through a webhook

When a configured Codemagic pipeline step calls a Notis webhook with artifact details, send the available file to a Telegram chat for review or handoff.

View example

Post Codemagic deployment notices to Telegram

Have a configured Codemagic workflow call a Notis webhook with deployment details, then send a concise Telegram notice to the team.

Supported Triggers and Actions

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

Codemagic triggers

Telegram actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Answer Callback Query

Send an answer to an inline button callback, shown as a chat notification or alert.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Delete Message

Delete a message when chat permissions and service limits allow it.

ActionInstant

Edit Message

Edit text messages sent by the bot.

ActionInstant

Export Chat Invite Link

Generate a new primary chat invite link, revoking the previous one.

ActionInstant

Forward Message

Forward a message from a chat.

ActionInstant

Get Chat Info

Retrieve current information about a chat.

ActionInstant

Get Chat Administrators

Retrieve the administrators of a group or channel.

ActionInstant

Get Chat History

Retrieve messages sent in a chat since the bot joined.

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.