Keep customer-impact reports from getting lost
Turn a short message about customer disruption into a trackable incident.
Trigger
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.
Action
Create Incident V2
Tool to create a new incident in incident.io using the V2 API. Use when you need to report and track an operational issue or outage. Requires at minimum an idempotency_key and visibility setting. Optionally specify severity, incident type, custom fields, role assignments, and other attributes.
Why this helps
A customer-impact note may get buried before anyone records who or what is affected.
- Give customer-impact reports a durable home.
- Preserve reported symptoms and affected users for responders.
- Reduce repeated questions about what the first report said.
Setup
Build it in a few focused steps.
- 1Connect Telegram and incident.io to Notis once through the portal.
- 2Create the automation in the portal or ask Notis to make it conversationally.
- 3Tell Notis in one plain-language instruction to create an incident when a Telegram message reports a customer-facing disruption and retain the stated impact.
- 4Select New Message Received and choose a channel for run reports.
- 5Test with a real, non-sensitive customer-impact example.
Questions about this workflow
What information is kept?
Notis can use the message context to summarize the reported experience and impact in the incident.
Can the workflow distinguish customer impact from general discussion?
Include examples of customer-impact reports in the plain-language instruction so Notis has clear guidance.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Telegram to incident.io. A trigger fires from one place; an action lands in another.
Telegram triggers
incident.io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Alert Attribute V2
Tool to create an alert attribute in incident.io. Use when you need to define structured data fields that can be parsed from alerts coming in via alert sources. Alert attributes allow you to extract and organize information from incoming alerts.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Alert Route V2
Tool to create an alert route in incident.io. Use when you need to configure how alerts should be processed, routed, and potentially converted into incidents based on conditions, grouping rules, and templates.
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 Alert Source V2
Tool to create a new alert source in incident.io. Use when you need to set up a new integration for receiving alerts from external systems via HTTP webhooks or manual entry.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
Create Catalog Entry V2
Tool to create a catalog entry in incident.io. Use when you need to add a new entry to a catalog type with specific attribute values. Catalog entries represent items like teams, services, or custom resources in your incident management workflow.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
Create Catalog Entry V3
Tool to create a catalog entry in incident.io using the V3 API. Use when you need to add a new entry to a catalog type with specific attribute values. Catalog entries represent items like teams, services, or custom resources in your incident management workflow.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Create Catalog Type V3
Tool to create a new catalog type in incident.io V3 API. Use when you need to define custom resource types for your organization's catalog, such as teams, services, or infrastructure components.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
Create Custom Field Option
Tool to create a new custom field option in incident.io. Use when you need to add a new selectable value to an existing custom field.
Create Custom Field V2
Tool to create a custom field in incident.io using the V2 API. Use when you need to add a new custom field to track additional information during incidents.
Connect any two apps with Notis in the middle.
Telegram and incident.io, 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 incident.io.