Add Telegram chat details to scheduled AgentQL reviews
Make the destination chat easy to verify during recurring work. Notis can retrieve current Telegram chat details alongside an AgentQL check.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Chat Info
Get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.).
Why this helps
Similar chat names or changed usernames can make it harder to tell whether an automation is using the intended Telegram destination.
- Show current chat identity in an operational review.
- Reduce confusion between similarly named chats.
- Keep the destination context close to research findings.
Setup
Build it in a few focused steps.
- 1Connect AgentQL and Telegram once in Notis.
- 2Create an automation in the portal or tell Notis what to automate from any channel.
- 3In one instruction, describe the AgentQL task and ask Notis to include current details for the specified Telegram chat in the run report.
- 4Choose a recurring schedule and select where Notis should send run reports.
- 5Test once and verify that Notis can retrieve details for the intended chat.
Questions about this workflow
What chat details are returned?
Telegram can return up-to-date information such as a chat's current name and username, depending on the chat.
Does this post a message?
No. This workflow retrieves chat information for the Notis run report.
Can this detect a changed chat name?
It retrieves current details. Detecting a change requires a previous value to compare against.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agentql to Telegram. A trigger fires from one place; an action lands in another.
Agentql triggers
Telegram actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Answer Callback Query
Use this method to send answers to callback queries sent from inline keyboards. the answer will be displayed to the user as a notification at the top of the chat screen or as an alert.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Message
Delete a message, including service messages, with certain limitations.
Edit Message
Edit text messages sent by the bot.
Export Chat Invite Link
Generate a new primary invite link for a chat; any previously generated primary link is revoked. the bot must be an administrator in the chat for this to work and must have the appropriate administrator rights.
Forward Message
Forward messages of any kind. service messages can't be forwarded.
Get Chat Info
Get up to date information about the chat (current name of the user for one-on-one conversations, current username of a user, group or channel, etc.).
Get Chat Administrators
Get a list of administrators in a chat. on success, returns an array of chatmember objects that contains information about all chat administrators except other bots.
Get Chat History
Get chat history messages. note: this uses the getupdates method with specific parameters to retrieve historical messages.
Connect any two apps with Notis in the middle.
Agentql and Telegram, 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 Telegram.