Combine Telegram conversation context with AgentQL findings
Research is easier to act on when it reflects the team's recent discussion. Notis can retrieve accessible Telegram history and use it to frame the latest AgentQL findings.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Chat History
Get chat history messages. note: this uses the getupdates method with specific parameters to retrieve historical messages.
Why this helps
Website checks and team conversations often live in separate places, so the reason behind a research task gets lost.
- Ground updates in accessible recent conversation context.
- Connect research findings to current team priorities.
- Reduce manual context gathering before review.
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, specify the AgentQL task and the Telegram history context to retrieve, then ask Notis to summarize relevant findings in the run report.
- 4Choose a recurring schedule and select where Notis should send run reports.
- 5Test with an accessible chat and confirm the retrieved context is relevant and appropriate.
Questions about this workflow
Can the bot retrieve history from any chat?
It can retrieve history only where the connected bot and Telegram method can access it.
Does this post the summary into Telegram?
This workflow uses Telegram history retrieval and places the research summary in the Notis run report. Ask for a separate Telegram message action if you want a chat post.
How should the history be used?
Specify the chat and the kind of recent context that matters, such as open questions or decisions relevant to the website task.
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.