X Spaces alerts: know when a KOL goes live

Quick answer: A Spaces alert fires when a tracked account shares a Space in a post — the announcement, the "we're live" post, the scheduled-Space card. The alert carries the title, whether it is live, the listener count and a direct join link, delivered to Discord or Telegram. Be clear about the boundary, because it decides whether this is useful to you: this is post-driven. A host who opens a Space and never posts about it, or a KOL who joins someone else's Space as a speaker, produces nothing to detect.

Why Spaces are worth catching at all

A lot of what happens in a Space never becomes a post. Calls get made out loud, project teams answer questions they would not answer in writing, and narratives get set in a room of two thousand people that leaves no searchable record. If you only read timelines, that entire surface is invisible to you.

The asymmetry is also unusual: a Space is one of the few crypto events where being present beats being fast. You cannot catch up on a Space the way you catch up on a thread. Either you were in the room while it mattered or you are reading someone's summary afterwards, and summaries are written by people who were early.

What the alert actually contains

When a tracked account posts something carrying a Space card, the alert surfaces these fields:

• Title — what the host called it. Often the most informative field, because hosts title Spaces after what they intend to discuss.
• State — a live Space is badged as such. A scheduled one shows its state instead, which is your cue to set a reminder rather than drop everything.
• Listener count — how many people are already in. This is the field most people underuse. Four hundred listeners on a Space by an account with modest reach means something is happening that reach does not explain.
• A join link straight into the Space, so you are one tap from the room rather than hunting for it.

The whole thing lands in the same channel as your other alerts for that account, so a Space announcement sits in context next to the posts around it.

The honest limitation

This is post-driven detection, and it is worth stating plainly rather than discovering later. The alert exists because the account posted something containing a Space card. That covers the common case well — hosts almost always announce, because a Space with no audience is pointless, and the announcement is exactly what carries the card.

What it does not cover:

• A Space opened silently. No post, no card, no alert. Rare for anyone trying to draw a crowd, but it happens with small or impromptu rooms.
• A tracked account joining someone else's Space as a speaker. The card belongs to the host's post, not to your account's activity. If they do not post about joining, there is nothing attached to them to detect.
• What is said inside. There is no transcript and no listening. The alert gets you into the room; the room is on you.
• A Space that ends. You are told it started, not that it finished.

If your requirement is "tell me whenever this person is speaking anywhere", no tool built on public post data can fully deliver that, and you should be suspicious of one that claims to.

Making it actually useful

Spaces alerts have a property that makes them different from post alerts: they are time-critical but low-volume. A KOL might post forty times a day and host a Space twice a month. That combination changes how you should configure them.

• This is the alert worth pinging a role for. Post alerts fire constantly and pinging on them trains everyone to mute. A Space happens rarely and expires — it is the textbook case for an actual notification.
• Keep the account list tight. Ten accounts whose Spaces you would genuinely drop things for beats a hundred you would not.
• Watch the scheduled ones differently. A scheduled Space is a calendar item, not an interrupt. A live one is the opposite.
• Read the listener count against the host. It is a crowd-size signal you get before joining, and unusually high attendance is often the actual news.

The rest of the room

The Space itself is only half the event, and the other half is often more actionable. Around a live Space you will typically see the host posting the link, people quoting it, and — the part that matters — contracts and links appearing in the replies underneath while the room is talking. That traffic is ordinary post activity and is caught by ordinary reply tracking.

So the useful configuration is not "Spaces alerts" on their own. It is Spaces plus reply and quote coverage on the same accounts, so you are told the room opened and you see what gets dropped under it. Contract detection runs on those replies, so an address mentioned during a Space and posted underneath arrives with its chain and market data already attached. For non-English hosts, translation applies to the surrounding posts too, even though the audio is beyond reach.

Setting it up

1. Open @x_relay_bot on Telegram, or add X-Relay to a Discord server.
2. Add the accounts whose Spaces you would actually attend. Be ruthless here — this list should be short.
3. Enable full activity coverage on them so the announcement post is caught, along with the replies around it.
4. Route them to a channel you have notifications enabled on, and consider a role ping for this one specifically.

Because Spaces are infrequent, test the setup against posts rather than waiting for a Space. If ordinary posts from those accounts are arriving, the Space announcement will arrive too — it travels the same path. There are more setup walkthroughs in our guides and comparisons.

FAQ

Reply tracking → · Auto-translate → · Guides and comparisons → · Pricing →