Quick overview
This workflow scans newly listed Solana tokens from DexScreener, filters them through RugCheck, Solana RPC, and Jupiter sellability checks, optionally scores risk with TypeSafe Jev or OpenAI, and posts Telegram alerts, 1h/24h rug warnings, plus a daily scorecard using an n8n Data Table.
How it works
- Runs every 5 minutes to pull the latest token profiles from DexScreener, fetches Solana pair data, and keeps only tokens that meet liquidity, 24h volume, and age thresholds.
- Checks each candidate token against RugCheck, queries Solana RPC for mint authorities and top holder concentration, and requests a Jupiter quote to confirm the token is sellable and the price impact is acceptable.
- Sends tokens that pass the hard safety gates to TypeSafe Jev (optional) or OpenAI to score impersonation, hype/promises, project substance, and overall rug-pull risk.
- Logs every evaluated token (alerted, held back, or blocked) to an n8n Data Table, and posts a formatted Telegram alert for tokens that meet the alert criteria.
- Runs every 15 minutes to re-check logged tokens at 1-hour and 24-hour checkpoints via DexScreener and Jupiter, updating outcomes and sending Telegram warnings if liquidity collapses or sell routes disappear.
- Runs daily at 9am to compile a Telegram scorecard from the Data Table showing yesterday’s alerted/blocked/held totals, 1h/24h failure rates, and rule hit rates over the configured lookback window.
- Triggers on workflow errors and sends a Telegram notification when the failure likely needs manual action (for example, credential, Data Table, or Telegram configuration issues).
Setup
- Add a Telegram bot credential and set the target chat ID in
telegramChatId for all Telegram message steps.
- Provide either a TypeSafe Jev bearer token (for the TypeSafe HTTP request) or an OpenAI API credential (for the OpenAI HTTP request), and set
useJev in Config to choose which reviewer to use.
- Ensure the workflow can reach the public APIs used (DexScreener, RugCheck, Jupiter) and set a reliable Solana
rpcUrl (for example, Helius/QuickNode) to reduce rate limits.
- Review and adjust thresholds in Config (liquidity/volume/age limits, holder concentration, LP lock minimum, insider/dev limits, checkpoint timings, and
tableName), then activate the workflow so it can create the n8n Data Table on first run.