posty.my
Sign in
Telegram in → scheduled posts out • queue + routing

Ship content from Telegram
to Pinterest, Mastodon, and Tumblr

Stop manual reposting. posty.my gives you routing, filters, scheduling, a queue, retries, and per-account AI captions — in one dashboard.

Sign in See features
routing scheduling retries per-account AI

Built for creators, SMM teams, agencies, and multi-brand workflows.

Pipeline
From Telegram to platforms — with control
Routing, queue, and per-account prompts.
Telegram channel posts in Queue routing • retries • status Pinterest scheduled Mastodon scheduled Tumblr scheduled
Dashboard preview
Routing, queue, and publishing status at a glance
Pending, failed, and next jobs in one view.
Open dashboard
Queue
live status
pending
12
processing
2
done
348
failed
1
Latest
Pinterest · account #1 · image
done
Mastodon · account #2 · photo
pending
Tumblr · account #3 · photo
failed
Per-account AI captions
Keys per user. Prompts per account.
Example prompt
Write a short Pinterest caption (1–2 sentences) + 3–6 hashtags. No hype.
Routing
Only selected Telegram bots can feed an account.
bot: news bot: deals account: pinterest‑home
The pain
Manual reposting doesn’t scale
  • - Copy/paste across platforms eats time
  • - Cadence breaks: windows, time zones, deadlines
  • - No visibility: what’s queued, what failed, what shipped
  • - Captions don’t fit each platform or niche
The fix
A single pipeline from Telegram to platforms
Routing
Map bots to accounts. Each account has its own rules.
Scheduling
Intervals or time slots, with jitter and guardrails.
Queue
Status, retries, failures, and audit trail.
AI captions
Provider keys per user, prompts per account.

Everything you need

Multi-account, multi-niche

Different accounts can have different filters, schedules, and AI prompts.

Routing via Telegram bots

Choose which bots can feed each account. No bot → no posts.

Scheduling that’s predictable

Interval or time slots, plus optional jitter to avoid “too exact” patterns.

Queue + observability

Pending / processing / done / failed / skipped with error details.

AI captions

Bring your own provider. Keys are private per user; prompts are per account.

Safe controls

Feature toggles, retention, and admin/client split.

How it works

1) Connect accounts
Add social accounts.
2) Route Telegram bots
Map bots to accounts.
3) Publish on schedule
Workers publish on schedule. Track in queue.

Who it’s for

For teams that need controlled, predictable publishing.

Best for
Creators & studios
Consistent publishing across platforms.
  • ✓Reusable schedules for different content streams
  • ✓Per-account tone via prompts (BYO AI keys)
Best for
SMM teams
Queue visibility, errors, and retries.
  • ✓Clear statuses and error messages
  • ✓Routing rules that prevent cross-posting mistakes
Best for
Agencies & multi-brand ops
Client isolation by account and rules.
  • ✓Account-level isolation by design
  • ✓Different prompts per niche/client
Best for
E-commerce & catalogs
Separate feeds and schedule by account.
  • ✓Separate streams by bot + account routing
  • ✓Predictable cadence with time slots/intervals
Best for
Media & publishing
Statuses, failures, and audit trail.
  • ✓Operational visibility in a single queue
  • ✓Fewer missed windows, fewer manual steps
Best for
Operations & admins
Routing rules, account settings, observability.
  • ✓Clear separation between client and admin areas
  • ✓Safe toggles per platform and workflow

Pricing

Simple tiers for different workflows. Sign in to get access.

Free
Free
Starter plan for first workflows.
  • - Routing + queue visibility
  • - Scheduling basics
  • - Up to 3 connected accounts
Sign in
Most popular
Pro
USD 9.99 / mo
More accounts and per-account prompts.
  • - Multi-account workflows
  • - Per-account prompts
  • - Up to 10 connected accounts
Sign in
Business
USD 29.99 / mo
Highest limits for multi-brand teams.
  • - Higher limits
  • - More automation
  • - Up to 50 connected accounts
Sign in
Pricing is indicative and may change.
Get started
Ready to turn Telegram into a publishing pipeline?
Sign in, connect accounts, and start scheduling.
Sign in View pricing

FAQ

Do you support different prompts per account?
AI prompt is configured per social account.
Are AI provider keys shared?
No. Keys are stored per user.
What if a post fails?
Check queue error, fix config, retry.
Sign in
Terms · Privacy