Morning news digest from Telegram channels
You follow a handful of Telegram channels, and every morning they compete for your attention post by post. Connect them to AIP once, and Claude reads all of them for you — one prompt, one digest, grouped by what actually matters to you.
What you need
One per channel you follow — each reads a public channel through the shared AIP reader account, no personal Telegram login involved.
The digest works the same in the Claude apps, Claude Code, Codex, or anything else that connects over your AIP URL.
Telegram channels are custom integrations, which are part of Pro.
How it works
Each Telegram channel you add becomes its own integration in AIP, reading the
channel through a shared AIP reader account — public channels only, and you
never hand over your own Telegram login. Agents see two read-only tools per
channel: list_posts pages through recent posts newest-first, and get_post
fetches a single post by its t.me link. Tool names carry the channel name, so
Claude can tell your channels apart and pull from all of them in one run.
Nothing is pushed or scheduled behind your back: the digest happens when you ask for it. In the morning, one prompt fans out across every channel you connected, and Claude merges the results into a single read — deduplicated, grouped, with links back to the original posts.
Set it up
- Open the dashboard, go to Integrations, and add a Telegram channel — paste the public channel’s name, AIP checks it exists. Repeat for each channel you follow.
- Switch on
list_postsfor the agent that builds your digest. Like every tool in AIP, each channel can be set to Allow, Confirm, or Hide — per agent, so a work agent can see work channels only. - Ask for your digest. Save the prompt you like as a snippet, or pin it in your client, and mornings become one message long.
Good to know
Posts are external content: AIP marks them as untrusted, and the tool descriptions tell agents not to follow instructions embedded in posts. Media attachments come through as temporary download links, and an album arrives as one post carrying all of its files. Reading is paginated at up to ten posts per page, and the agent follows a cursor for older history when you ask for a longer lookback.
What to ask your agent
Once everything is connected, prompts like these do the work: