Skip to content
Notis

Confirm the Telegram destination for archive research

Reduce misdirected research handoffs by checking the current chat information before sharing.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

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

A stale chat name or username can make it harder to tell whether research is going to the intended conversation.

  • Retrieve current information about the specified Telegram chat.
  • Make the intended destination easier to verify before a handoff.
  • Pair Archive.org research requests with a clearer chat destination check.

Setup

Build it in a few focused steps.

  • 1Connect Archive.org and Telegram once in the Notis portal.
  • 2Create an automation in Automations, New Automation, or tell Notis to create one in plain language.
  • 3In one instruction, ask Notis to check the specified Telegram chat details and summarize the Archive.org research request for that destination.
  • 4Choose a webhook trigger and select where run reports should go.
  • 5Test with one real chat identifier and confirm the returned chat details match the intended destination.

Questions about this workflow

Does checking chat info send a message?

No. This action retrieves current chat information. Add a separate message action if you want to deliver research in the same automation.

What identifier is needed?

Provide the chat identifier that the Telegram connection can use.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Archive.org to Telegram. A trigger fires from one place; an action lands in another.

Archive.org triggers

Telegram actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Delete Message

Delete a message, including service messages, with certain limitations.

ActionInstant

Edit Message

Edit text messages sent by the bot.

ActionInstant

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.

ActionInstant

Forward Message

Forward messages of any kind. service messages can't be forwarded.

ActionInstant

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.).

ActionInstant

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.

ActionInstant

Get Chat History

Get chat history messages. note: this uses the getupdates method with specific parameters to retrieve historical messages.

ActionInstant

Connect any two apps with Notis in the middle.

Archive.org 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.