SkillAgentSearch skills...

Userbot

Telegram Userbot built with Pyrogram

Install / Use

/learn @athphane/Userbot
About this skill

Quality Score

0/100

Supported Platforms

Universal

README

Pyrogram Userbot

Python Version Repo Size Commit Activity Codacy Badge HitCount Contributors Last Commit Issues Pull Requests License

<img src="https://i.imgur.com/WXUgDHT.png" width="160" align="right">

A Telegram Userbot based on Pyrogram

This repository contains the source code of a Telegram Userbot and the instructions for running a copy yourself. Beside its main purpose, the bot is featuring Pyrogram Asyncio and Smart Plugins; feel free to explore the source code to learn more about these topics.

I assume you will read this whole README.md file before continuing.

Requirements

You're gonna need to get the following programs and services either installed on your server or signed up for. You must do all. It is a cardinal sin if you don't.

  • Python 3.10 (requirements were generated for 3.10. Python 3.8 is supported from the looks of it.)

  • virtualenv installed so that the packages don't interfere with other system packages.

  • MongoDB on your server or a free server from MongoDB Atlas. (I recommend Atlas as I used it during development with no issues.)

  • carbon-now-cli on your server too generate code images for the carbon.py module. I use this CLI tool cause I don't know and couldn't get selenium and chromedriver to work nicely on my server/code. I'll be nice and even give you the command to install this. I assume you already have NPM installed.

    Windows: npm install -g carbon-now-cli
    Linux: sudo npm install -g carbon-now-cli --unsafe-perm=true --allow-root
    MacOS: I assume almost the same as linux ¯\_(ツ)_/¯
    

Installation and Deployment

The way I deploy

git clone https://github.com/athphane/userbot.git
cd userbot
virtualenv venv
source venv/bin/activate
pip install -r requirements.txt
python -m userbot

Using docker

  • Save the following content as docker-compose.yml
services:
  userbot:
    hostname: userbot
    volumes:
      - ./config:/root/userbot/config
    image: ghcr.io/athphane/userbot:latest
    restart: always
    depends_on:
      - userbot-mongo
  userbot-mongo:
    image: mongo:latest
    hostname: userbot-mongo
    restart: always
    volumes:
      - ./mongo:/data/db
    environment:
      - MONGO_INITDB_DATABASE=userbot
      - MONGO_INITDB_ROOT_USERNAME=userbot
      - MONGO_INITDB_ROOT_PASSWORD=userbot-password
mkdir config
wget -O config/userbot.ini https://raw.githubusercontent.com/athphane/userbot/refs/heads/master/userbot.ini.sample
nano config/userbot.ini
  • First run:
docker compose run --rm userbot python -m userbot
  • Configure userbot and stop container CTRL+C
  • Run the container again de-attached:
docker compose up -d

Spotify integration

To get the Spotify commands working on the Userbot, you need to get a CLIENT_ID and CLIENT_SECRET form the Spotify Developer Portal and add them into your userbot.ini file.

On the Spotify developer portal, make sure to set your application Redirect URI to 'http://localhost:8888/callback'.

Now is a good time Then go ahead and run the command python spotify.py in the projects root directory.

This will create a file called .cache-yourusername. You need to transfer this file to the project root of the server that will be running your userbot. This is a one time setup.

Known issues

Star History

<a href="https://star-history.com/#athphane/userbot&Date"> <picture> <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=athphane/userbot&type=Date&theme=dark" /> <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=athphane/userbot&type=Date" /> <img alt="Star History Chart" src="https://api.star-history.com/svg?repos=athphane/userbot&type=Date" /> </picture> </a>

Credits, and Thanks to


<p align="center">Made with love from the Maldives ❤</p>

Related Skills

View on GitHub
GitHub Stars181
CategoryDevelopment
Updated5d ago
Forks114

Languages

Python

Security Score

100/100

Audited on Mar 27, 2026

No findings