Hourly crypto Twitter buzz and price alerts in Slack

Build me an hourly crypto social signal agent that pings me in Slack only when crypto Twitter chatter and on-chain price action are both moving. Trigger should be a cron that runs once an hour.

Each run, do the following:

1. Use TwitterAPI.io Advanced Search to pull tweets from the last hour matching a configurable query. The default query should be: (crypto OR bitcoin OR ethereum OR altcoin) min_faves:50 lang:en -is:reply. Cap the result at the most recent ~100 tweets.

2. From those tweets, extract every mention of a coin: both ticker symbols like $BTC, $SOL, $ETH and plain coin names like Bitcoin, Ethereum, Solana. Normalize casing, strip the dollar sign, merge ticker and name mentions for the same coin (for example $BTC and bitcoin both count toward BTC), and dedupe so each coin has a single mention count for the hour. Save one representative tweet URL per coin (pick the highest-engagement tweet for that coin).

3. For each coin that crossed the mention threshold (default 5 mentions in the hour), call CoinGecko Search to resolve the ticker or name to a canonical CoinGecko coin id. Prefer the highest-market-cap match when more than one coin shares a symbol.

4. Call CoinGecko Coins Markets in a single batched call with the resolved ids to fetch current price (USD), 1-hour price change, 24-hour price change, and 24-hour volume.

5. Surface only coins that meet BOTH bars at the same time: chatter bar = at least 5 mentions in the hour, AND market bar = either a 24-hour price change above 5 percent (absolute value) OR a notably elevated 24-hour volume. Make all thresholds configurable inputs.

6. If anything qualifies, use Slack Send a Message to post a single ranked message into a configurable channel. Rank by mention count, then by 24-hour price change. For each coin include: name, ticker, current price, 24-hour percent change, mention count, and the representative tweet link. Use Slack mrkdwn formatting and keep the message compact.

7. If nothing qualifies that hour, the workflow should stay quiet and post nothing. Do not send an empty or 'no signals' message.

Inputs the user should be able to edit: the X search query, the lookback window, the mention threshold, the 24-hour price-change threshold, the volume-jump threshold, and the destination Slack channel.