Telegram Actor

Telegram Scraper

Pull public Telegram channel or group messages and metadata where the source is publicly accessible.

Social Media

What it does

Pull public Telegram channel or group messages and metadata where the source is publicly accessible.

Best for

  • Public channel monitoring
  • Message research
  • Alert workflows

Fields

  • Message text
  • Message URL
  • Channel name
  • Date
  • View count when public
  • Public metadata

Inputs

  • Public channel URLs
  • Date range when supported
  • Max messages
README

Telegram Scraper technical notes

Telegram Scraper can be used as part of a reviewed Apify workflow to collect public Telegram data, clean the dataset, and deliver it to business tools. The exact setup depends on the target, available data, and required output structure.

Use Cases

  • Public channel monitoring
  • Message research
  • Alert workflows

Data Fields

  • Message text
  • Message URL
  • Channel name
  • Date
  • View count when public
  • Public metadata

Inputs

  • Public channel URLs
  • Date range when supported
  • Max messages

Workflow

  • Public Telegram source
  • Actor run
  • Clean dataset
  • Delivery destination
  • Business report or automation

Delivery

  • CSV
  • Excel
  • Google Sheets
  • API
  • Database
  • Airtable
  • Notion
  • Slack
  • CRM

Limitations

  • Availability depends on the target website or platform structure.
  • Some data may not be publicly available.
  • Some requests may not be suitable.
  • The workflow is reviewed before setup.

Setup Notes

  • Use public channel or public group URLs that can be accessed without private membership.
  • Set date range and max messages to match the monitoring or research window.
  • Clarify whether forwarded messages, media captions, or only text messages are needed.

Output Handling

  • Store channel name, message URL, message text, date, and public view counts together.
  • Messages may need text cleaning, language detection, or topic tagging before reporting.
  • View counts and edits can change after collection, so delivery timestamps matter.

Quality Checks

  • Verify that input channels are public and reachable.
  • Check whether messages include deleted, edited, or forwarded content that needs special handling.
  • Deduplicate records by message URL before delivery.

FAQ

Can The Scrape Lab configure Telegram Scraper for me?

Yes. We review the target, configure inputs, run tests, clean the output, and connect delivery where needed.

Can this run on a schedule?

In many cases, yes. Recurring schedules are reviewed based on the target, frequency, and reliability requirements.

Can the output go to Google Sheets or a CRM?

Yes. Delivery can be set up to Google Sheets, CSV, Airtable, databases, APIs, Slack, CRMs, or other tools depending on your workflow.

Is every request suitable?

No. We focus on public data and review each request before setup. Some targets or data requests may not be appropriate or technically reliable.

Need data collected or piped somewhere?

Send the source and fields. We'll review the scraper, Actor, or pipeline approach.

Request a Data Task