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-15. 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 soon the next round goes.
  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. Telegram groups, Oracles, Agenda («Replies to your posts are answered under this agenda.»).
  7. 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).

A group gets your next post once enough new messages have passed there since the last one, so busy groups see you more often. Answers to replies are AI runs; their cost shows in your AI spend: FE pipeline: See your AI spend

Mentioned