Use a Grok Bot Template for X Social Listening

Q: What do the five relevance buckets mean?

VERY_LOW through VERY_HIGH , assigned per mention by RedReplier's scoring. Filter to HIGH and VERY_HIGH for a digest a human will actually read, and use POST /mentions/{id}/explain when a score looks wrong.

Q: Why does the same mention keep appearing?

Its status is still NEW . Marking it APPROVED or REJECTED through PATCH /mentions/{id}/status takes it out of the new queue, which is why a listening setup without triage never feels finished.

There is an obvious objection to a Grok bot template for X social listening: Grok already reads X. It does, and it still does not solve the problem, because reading is not the hard part. Scoring, storing, deduplicating and triaging across days is the hard part, and that is what the RedReplier template adds on top.

The short version: install the template, paste a redreplier_ API token, then ask for "today's X mentions sorted by relevance". The bot calls GET /mentions with sources=TWITTER&sort=RELEVANCE.

A Grok bot template for X social listening is a share link that copies a configured Grok Bot, plus a skill describing the RedReplier REST API, into someone else's Grok Bot app. SpaceXAI turned on template sharing on 28 August 2026. Configuration crosses the link; your token, your keywords and your mention history do not.

This is the X-specific companion to the Grok bot template for social listening guide.

Why not just ask Grok to search X directly?

Grok searches X live and answers once. RedReplier keeps a scored, deduplicated record you can triage across days, which is a different job.

Live search against tracked listening

Ask Grok to search X

Answers this question, once
No score, no history
Same post resurfaces tomorrow
Nothing to mark handled

Ask through RedReplier

Five relevance buckets per mention
Status: NEW, APPROVED, REJECTED
Deduplicated across runs
POST /mentions/{id}/explain for the reasoning

The status field is the quiet win. Without it, every morning digest re-shows what you dealt with yesterday.

What does sorting by relevance actually change?

MentionSort takes RELEVANCE or RECENT, and on X the choice decides whether you get a digest or a firehose. X is the highest-volume source RedReplier monitors, so recency ordering surfaces whatever happened in the last ten minutes regardless of whether it matters.

Relevance ordering combines with scoreBuckets to cut the list to the mentions worth a human minute:

You:  Show me X mentions from today at HIGH or above, sorted by relevance,
      and explain why the top two scored that way.
 
Bot:  GET  /mentions?sources=TWITTER&scoreBuckets=HIGH,VERY_HIGH
           &statuses=NEW&sort=RELEVANCE&from=2026-08-30
      POST /mentions/{id}/explain    (x2)
      -> 7 mentions, 2 explained, nothing changed

How do I install and test it?

Installing the RedReplier Grok bot template takes four steps: open the share link in Grok Bot, create a redreplier_ API token, paste it into the credential field, and ask for today's X mentions as a read-only test.

From share link to first X digest

Open the link on a device with Grok Bot installed. Press "Add to Grok Bot" on x.ai/bot/8aU6ly_uunnMabpybs3hB.

Create a RedReplier API token. It starts with redreplier_ and needs a paid plan with API access.

Paste it into the credential field, not the chat. Anything typed into a message stays in the conversation.

Ask for "today's X mentions sorted by relevance". That exercises GET /mentions and writes nothing.

Step 4 is read-only by design. Confirm the read path works before the bot touches a status.

Can the bot watch X and Bluesky together?

Yes. sources is an array, so one call covers TWITTER and BLUESKY in a single request, and the response labels each mention with its source. That pairing is worth setting up, because the same conversation now happens on both and following only one gives you half of it.

RedReplier monitors six sources in total: REDDIT_POST, REDDIT_COMMENT, TWITTER, BLUESKY, HACKERNEWS and FACEBOOK.

One query, several sources

You name the sources

GET /mentions?sources=TWITTER,BLUESKY

Scored and deduplicated

One ranked list, labelled by source

Omit sources and you get all six, which on a busy keyword is more than a morning digest should carry.

Should the bot run on a schedule?

Run the RedReplier bot on a schedule for reading, never for deciding. On X specifically, a twice-daily run beats hourly, because relevance scoring needs a little time to see how a thread develops.

Name:      X listening digest
Schedule:  every weekday 09:00 and 16:00
What:      GET /mentions for new TWITTER and BLUESKY mentions since the last
           run, HIGH and VERY_HIGH only, sorted by relevance. Summarise each
           with a one-line reason and a direct link.
Approval:  never change a mention status on your own.
If empty:  do nothing, send no notification.

What breaks in the first week?

A 401 on the first call almost always means the plan lacks API access rather than a bad token. Leaving sort unset gives you RECENT behaviour on the noisiest source you track. And keywords added through the API sit in PENDING until activated, so a fresh keyword monitors nothing and looks like a broken integration.

RedReplier

–

Catch every buyer asking for what you sell

Get Started

Reddit, X, Bluesky & HN

Real-time intent alerts

Unlimited AI replies

Ranked by buyer intent

Why does the same mention keep appearing?

Its status is still NEW. Marking it APPROVED or REJECTED through PATCH /mentions/{id}/status takes it out of the new queue, which is why a listening setup without triage never feels finished.

Where do I find other Grok bot templates?

groktemplates.dev indexes Grok bot templates by use case. On this blog, the Reddit monitoring and lead finder guides cover the other jobs this template does.

Install the RedReplier Grok bot template and run a read-only X digest today, or read the API docs first.

Sources: the RedReplier OpenAPI spec, x.ai/bot, and @bot on X (28 August 2026). Checked 30 August 2026.