Review a Changed Coda Decision in Telegram
When a decision-register page changes, send supplied prior decision, new evidence, owner, and deadline for a reaffirm, amend, or reopen review.
Connect Coda to Telegram
When something happens in Coda, 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
Triggers when a document is deleted.
Do this · Action
Send an answer to an inline button callback, shown as a chat notification or alert.
Examples
Ways Notis can move work from Coda to Telegram
Turn a New Coda Initiative into a Telegram Launch Brief
When a new Coda initiative document arrives, send an approved Telegram brief with its owner, purpose, timing, and next decision.
Review a Deleted Coda Document in Telegram
When Coda reports a document deletion, send the supplied deletion facts and recovery owner to Telegram for disposition.
Explain Coda Task Changes in Telegram
When a tracked Coda page changes, send supplied before-and-after task facts to Telegram with the decision they require.
Share Decision-Ready Meeting Notes in Telegram
When a Coda meeting-notes page is created, send supplied decisions, actions, and open questions to an approved Telegram audience.
Poll on Recovery After a Coda Deletion
After a Coda deletion event, ask authorized Telegram respondents to choose the supplied recovery disposition.
Turn Supplied Standup Updates into a Telegram Triage
On a schedule, send supplied standup updates and prior-period baseline to Telegram, separating blockers from routine progress.
Announce Sprint Commitments from a New Coda Document
When a sprint document is created, send its supplied goal, dates, owners, and commitment gaps to an approved Telegram chat.
Route Supplied External Events to Telegram
When an authorized webhook arrives, send its supplied event, severity, entity, and triage context to Telegram.
Poll on a Coda Proposal Decision
When a supplied proposal page changes, send an authorized Telegram poll with its options, deadline, and decision owner.
Supported Triggers and Actions
Notis builds workflows that link Coda to Telegram. A trigger fires from one place; an action lands in another.
Coda 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
Deletes a Telegram message, subject to time, message type, and chat permissions.
ActionInstant
Coda Document Deleted Trigger
Triggers when a document is deleted.
TriggerPolling
Edit Message
Edits a Telegram message, subject to Telegram’s permissions and restrictions.
ActionInstant
New Coda Document Trigger
Triggers when a new document is created.
TriggerPolling
Export Chat Invite Link
Generate a new primary chat invite link, revoking the previous one.
ActionInstant
New Coda Page Trigger
Triggers when a new page is added to a document.
TriggerPolling
Forward Message
Forwards a Telegram message; service messages and protected content cannot be forwarded.
ActionInstant
Specific Coda Page Updated Trigger
Triggers when a specific page in a document is updated.
TriggerPolling
Get Chat Info
Retrieve current information about a chat.
ActionInstant
Get Chat Administrators
Lists chat administrators, excluding other bots.
ActionInstant
Get Chat History
Polls pending bot updates and filters the batch; this is not complete chat history.
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 schedule (recurring or one-time), and a change in one of your Notis databases.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ 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
Scheduled triggers
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Daily · 8:00Weekdays onlyOnce · Dec 13
Beta
Database triggers
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Row addedProperty editedValue > limit
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
All12Manager5Telegram1Messages0WhatsApp2Email4Slack8
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Related pairs
More ways to connect Coda and Telegram
Connect any two apps with Notis in the middle.
Coda and Telegram, or any other combination from 1,500+ 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 Telegram.