FE pipeline: Post your posts into groups at a pace set by their traffic and follow what was sent and deleted

Web app as of 2026-10-24. API layer: API pipeline: Post your posts into groups at a pace set by their traffic and follow what was sent and deleted

Goal: post your posts into groups at a pace set by their traffic and follow what was sent and deleted.

Before you start: a Pro project, your posts (Cabinet → My Posts), groups your oracles can write in, Telegram account oracles, and an agenda that answers replies.

  1. Cabinet → My Campaigns → New, Kind: Announcements.
  2. Project; Posts (posts or workspaces of them).
  3. Speed: X-Slow … X-Fast — how often your posts go out overall.
  4. Order: Linear (groups in turn) or Magnet (largest groups first).
  5. Delivery: Send as message, or forward the original Telegram post (only for posts Cabi.Chat imported from Telegram).
  6. Groups the oracle is not in: Skip, or Join first, post later. Skip groups that delete more than, % with after at least, posts: the campaign stops posting into a group that deletes that share of your posts, once that many were sent there; you choose both numbers.
  7. Telegram groups, Oracles, Agenda («Replies to your posts are answered under this agenda.»).
  8. Create, then Start on its tile. It runs until you stop it.

Follow: tile ⋮ → Show performance: totals (Sent, Groups, Deleted %, Replied %), Timeline, per Group, and Messages with each send's Status: Deleted, Replied ×n or live. The posts sent are listed below («Sent announcements will appear here» until the first one).

Your posts are spread out so groups are not crowded: busy groups see you more often, quiet ones less. Each of your oracles also posts at its own pace, set on the oracle (Posting pace, FE pipeline: Connect a Telegram account as an oracle (phone → code → 2FA), start and stop it, sign it in again when Telegram asks). Answers to replies are AI runs; their cost shows in your AI spend: FE pipeline: See your AI spend

Mentioned