Bloom Twitter Tasks: Five Modes to Automate Crypto Trades from X on Solana and EVM

Bloom just shipped a major rework of Twitter Tasks. Three modes became five.You can now turn almost any action a tracked account takes on X into a trade trigger: a contract address in a screenshot, a quote of a specific tweet, a follow event, even a tweet deletion.

Examples in this guide use Solana; everything works the same way on EVM unless flagged.*

What changed

The Twitter Task modal now opens with five tabs:

• –CA Scanner. Triggers on a contract address posted by the tracked account.
• –Engagement. Triggers when the tracked account interacts with a specific tweet.
• –Follow / Unfollow. Triggers on follow or unfollow events between two accounts.
• –Posts & Replies. Triggers on any post, reply, retweet, or quote from a target.
• –Tweet Delete. Triggers when a specific tweet is deleted by its author.

CA Scanner

The successor to the old Buy CAs Posted mode. You set a Target Handle, an Amount, and the task fires a buy whenever that handle posts a contract.

Target Actions expand to four signal types now: original Tweets, Retweets (contract pulled from the original post), Replies, and Quotes. Quote is the new one.

Enable Use OCR if the target posts calls as screenshots. Bloom reads the contract address out of the image and triggers as if it were text.

Token Filters band the entry: Min/Max Market Cap, Min/Max Age with a dropdown for minutes, hours, or days. Platforms restricts the task to the launchpads you trust. Token Filters, OCR, and Platforms live on this mode only.

Practical example: you track a Solana KOL with a track record of posting CAs as screenshots. Set CA Scanner, enable OCR, cap the market-cap band, attach Auto Orders to take profit at 2x and stop loss at -40%, and walk away.

Engagement

Locks onto one specific tweet. The task fires when the target account replies to, retweets, or quotes that tweet.

You pre-set the Token Address. Engagement is the right mode when you already know which token your thesis depends on and you are waiting on a particular public reaction to confirm conviction.

Three Target Actions: Reply, Retweet, Quote. Pick one or several.

Practical example: a foundation posts the official ticker tweet for a new launch. You set Engagement on the announcement tweet ID, the token address, and the founder's handle as Target. The buy fires only if the founder visibly endorses the tweet.

Follow / Unfollow

Tracks a relationship change on X. You set a Follower Account and a Followed Account. The task fires when the Follower Account follows or unfollows the Followed Account.

Direction toggles between Buy and Sell on the same task, so a follow can fire an entry while an unfollow fires the exit on the same wallet. Useful for treating follows and unfollows as entry or exit signals.

Practical example: you read a team detaching from a project on X as the leading indicator of a rug. Set Follow / Unfollow with the team's main account as Follower, the project's account as Followed, Direction = Sell. The task closes your position the moment the team unfollows the project.

Posts & Replies

The most flexible of the new modes. The task fires when a target account posts, replies, retweets, or quotes.

The control surface is wider here. Original Poster narrows interactions to those involving a specific account's tweets, so you only fire on, say, the target's replies to a particular founder, not their replies to anyone. Text Keywords narrow the trigger further: set inclusion keywords (the tweet must contain at least one) and exclusion keywords (the tweet must not contain any). Separate keywords with commas.

Use Direction to pick Buy or Sell on the signal.

Practical example: track a macro account, fire a Buy only when their post or reply contains ETF, approved, or SEC, and exclude tweets that contain rumor or speculation.

Tweet Delete

Triggers when a specific tweet, identified by URL or numeric ID, is deleted by its author. Direction sets Buy or Sell, so the deletion can fire either side of the trade.

Tweet Delete is built for one job: treating a deletion as information. A high-profile call that gets nuked minutes after going live tells you something, and you can have your exit fire before the room reacts.

Tweet Delete is the only mode excluded from Mass Create, because the trigger by definition needs a specific tweet identifier.

Auto Orders attached to every task

Every Twitter Task carries Auto Order Groups directly inside its modal. Create the Group, drop one or more Auto Orders inside, and the task ships with the full lifecycle baked in.

This collapses the previous two-step workflow (create the buy, then go set take-profit and stop-loss separately) into one task. The buy fires, the exits run off the same configuration, and the trade runs to its planned exit on its own.

Mass Create across four modes

Mass Create supports CA Scanner, Engagement, Follow / Unfollow, and Posts & Replies. Paste handles into Target Handles, one per line, and Bloom creates one task per valid handle, all sharing the same configuration.

If you want to scan 50 KOLs for CA posts with identical filters, this is the path. Configure once, deploy fifty.

The Explanation panel

Each task modal exposes an Explanation panel that translates your configuration into a plain-text description of what the task will actually do. Missing fields and invalid settings are flagged in red before you save. Use it as a sanity check on complex setups, especially Posts & Replies with stacked Original Poster and Text Keywords filters.

Five modes, one configuration surface, Auto Orders attached at the source, Mass Create for breadth, and an Explanation panel that audits your setup before it goes live. That's the new Twitter Tasks stack in one breath.