blokboard/ Open app

EXAMPLE 09 OF 16 · Easy

Get new Pump launches on Telegram

Listen for new coins, optionally filter by creator, and send a readable launch alert through your Telegram bot.

Browser or DesktopPump.funTelegramConditionsEvents

Before you begin#

  • Choose Solana mainnet and a working RPC route in runtime settings. These examples read live data; illustrative results below will differ.
  • Create and select your bot using Telegram setup, then set chatId in Globals. Keep bot tokens in the connection.
  • Use an RPC route with WebSocket subscriptions. creatorFilter is * for all creators, or one exact creator public address.

WORKFLOW SNAPSHOT

Pump launch alerts

5 nodes

Interactive workflow preview loads here. Download the JSON to inspect it in the app.

Import creates an inactive copy. Set your own inputs and connections before running.

2 setup requirements
  • input: Set chatId in Globals
  • connection: Choose the telegram connection for send

Walk through the workflow#

  1. Start begins Watch new coins. Leave it running while waiting for a creation event; it does not list past launches.
  2. Code checks the creator filter and builds a message from the name, symbol, mint, creator, and signature.
  3. If sends only matching events down its true output. Telegram receives that path; the false path ends without sending.
  4. Stop after verifying an alert. Narrow creatorFilter before leaving a high-volume stream running.

Example alert#

New Pump coin: Example Coin, Symbol: EXAMPLE, Mint: the event’s mint address, Creator: the creator address, Transaction: the creation signature. Names and symbols come from the creator; use the mint to identify the coin.

Try the condition#

First observe one event with creatorFilter set to *. Copy a creator address into that Global and run again. Only future events from that creator pass. This is a concrete example of Code calculating a boolean and If choosing the path.

Keep it running#

The supplied listener stops after 300 seconds. Set Timeout to 0 for continuous listening after checking the output. Keep the selected runtime available; a listener has no historical catch-up in this example. High event rates can exceed Telegram’s delivery limits, so use a focused creator filter.

If no message arrives#

Inspect Watch new coins first. No events can mean a quiet filter or a subscription problem. An event at the watcher but no Telegram execution means the condition did not match. A failed Telegram node points to connection or destination setup.