X (Twitter) Mention Monitor

Most teams check mentions when they remember to, which means the one that mattered happened three days ago. This agent sweeps every hour, reads the thread a mention sits inside before judging it, and writes the Slack message with the reply angle already in it, so answering costs somebody a minute instead of an afternoon of context. It has no way to post on X, and that is deliberate.

What people use it for

• Quote tweets you would miss - Criticism on X migrates into quote tweets, where your notifications will never show it. The sweep reads those alongside your mentions, so the thread about you reaches you the same hour.
• An angle, not an alert - Anything can send you a link. This arrives with two or three sentences you could genuinely post and a note on which account should be the one posting them.
• Buying questions answered today - People ask in public whether your product does X before renewing with somebody else. Those questions land with the asker's follower count attached, so which to answer first is obvious.
• No bot speaks for you - Every reply that leaves your account still comes from a person with a name. The agent drafts, a human decides and posts, and that is the only version of this that does not end badly.

Before you fork

What access do we need on X?

An X developer app on a paid tier with read access to mentions, plus the Slack channel. Those read endpoints are metered, so an hourly schedule across two or three handles sits comfortably inside the entry tier while ten handles will not. Connect it and Test Run will show you what a single sweep pulls back, before you widen the list.

Can we let it reply once we trust it?

Not in this template. It holds four read operations on X and one Slack operation, and no write access to the platform exists in the workflow at all, so a rogue post is not a failure mode you have to plan around. Teams that want an approval loop keep it exactly like this and post from their phone in ten seconds.

How do we stop it pinging us all night?

Write your quiet hours into the ping policy and anything that fails to clear them waits. The one exception is the escalation rule, which sends outage claims, invoice screenshots and fast moving threads straight away whatever the policy says, since those get worse while you sleep. Either way the bill is one run an hour, found something or not.