X Automations

Recap

Recap is an add-on on a feed or phrase automation: a ranked summary of the posts it announced, sent into the group at set times of day, Eastern time.

Recap is an add-on on a feed or phrase automation: a ranked summary of the posts it announced, sent into the group at set times of day, Eastern time.

What recap is

Warning

Recap is not available on follow trackers.

Every post the automation announces is added to its recap list, which keeps the most recent 100.

The list survives a pause and a bot restart. Changing the automation's source — the handle, or the phrase and its gates — clears it.

Schedule and fields

Recap fields

FieldAcceptedDefault
Enabledon / offoff
TimesUp to 3 HH:MM times, Eastern (America/New_York)00:00
Rank byLikes, Views, Comments, Bookmarks, or FollowersLikes
Row templateUp to 500 charactersthe built-in row, below
HeaderUp to 500 charactersnone

The frequency dropdown — Once a day, Twice a day, 3× a day — sets how many times you can enter.

Send and missed slots

5 minutes before each slot the bot refreshes each post's counts. At the slot it sends the ranked list. A slot the bot cannot reach within 15 minutes is skipped — a missed recap is never sent late.

A slot with nothing queued sends nothing.

Recap goes to the automation's alerts topic when one is set (see 2.8), otherwise the group's General.

Row and header placeholders

Row tokens

TokenRenders to
{rank}Position after ranking, from 1.
{account}A link reading @handle.
{handle}@handle as plain text.
{followers}The author's follower count, compacted (e.g. 24.1K).
{likes}Likes, compacted.
{replies}Replies, compacted.
{views}Views, compacted.
{bookmarks}Bookmarks, compacted.
{tweet}A link whose visible text is the word "post".
{url}The raw post URL, as plain text.

The header supports one token: {count}, the number of posts in that recap.

The built-in row template, rendered

InputOutput
Template{rank}. {account} · {followers} · {likes} · {views} {tweet}
Rendered (rank 1)1. @kindachic · 24.1K · 1.2K · 41.8K post
Header with {count}, 3 posts→ 3

@kindachic links to the profile; "post" links to the post.

Long recaps split into several messages; the header appears on the first only.