Fiverr
Hire us for a guided setup, a repair, or a website help chat on a Fiverr order.
Open FiverrFor Creators and Admins · 1.1.1
Update Scheduler
Posts your updates and pictures at the times you set in a simple spreadsheet.
Sound familiar?
- You have to be online at the right moment just to post an update.
- Posts go out late, or twice, when you are busy.
- You keep a list of what to post, but nothing sends it for you.
How we tested it
We scheduled two posts in a real Telegram chat. Both went out on time, at 14:24 and 14:26.
What this shows
- Scheduled 14:24 → posted 14:24
- Scheduled 14:26 → posted 14:26
- From a CSV file
| Check | Result |
|---|---|
| Version | 1.1.1 |
| Tests | 21 tests passed on Linux and on Windows, plus a quick test run that did not send anything. |
| Linux | PASS |
| Windows | PASS |
| Docker | Not in this package |
| SHA-256 of the download | 2096fc90abbabdaf2983248650e5ad4ea3d5e98861e8d7f91b30ee795585a679 |
What you get
- A simple CSV spreadsheet for dates, times, images and captions
- A test run first that shows what would be sent, then a real send when you are ready
- After a successful send, the row is marked as sent and skipped next time. A crash between the send and that save, or a retried request, can still post twice
- Posts only to the chat you set up
- Runs with your own bot on your own computer
What You Need to Run This Tool
- A Windows or Linux computer or VPS you control — we don't host it for you
- Python 3.10 or later
- Your own Telegram bot token, the destination chat ID, and posting rights in that chat
- A CSV schedule and any local images the rows refer to
- Rows already marked sent (a
sent_atvalue, or status sent) are skipped. If the process crashes after Telegram accepts a post but before that mark is saved, or a request is retried after a timeout, the same row can go out twice. There is no zero-duplicate guarantee
Technical details
After a post goes out successfully, that row is marked as sent and skipped next time. This is best effort: if something stops after Telegram accepts a post but before that mark is saved, or a send is tried again after a timeout, the same row can go out twice. There is no promise that a post will never be sent twice. It needs Python 3.10 or later, your bot sign-in, the destination chat, and posting rights in that chat.
How it works
- Install the package in a Python 3.10+ environment.
- Prepare a CSV schedule and the images it refers to, on your computer.
- Run a test run against your schedule and confirm what would be sent.
- When you are ready, run a live send to a private destination you control.
How to set it up
- Unzip the download package and create a Python virtual environment.
- Install requirements.txt.
- Copy the example schedule, add your dates and image paths, and set your bot token and destination in the process environment.
- Run a test run first, then a live send when the test run looks right.
Packages
Download it yourself for $12 USD on Gumroad, or book setup help on Fiverr or Upwork.
Self-serve
$12 USD
download package, README, and a 7-day bug-fix window through Gumroad messages.
Basic
$25 USD
Scheduler package, isolated test run, example CSV, README, 7-day bug-fix support via Fiverr or Upwork messages.
Standard
$49 USD
Basic plus help preparing your first schedule and a test run against a copy of your CSV.
Premium
$89 USD
Standard plus a supervised first live send to your private destination and a 14-day support window.
Support stays on the platform you purchased through. Requirements: Python 3.10+ on Windows or Linux. You provide your own bot token and image files. Sepxo Labs does not receive your tokens or media.