Bear Brown
← All N8N workflows
AI & researchAgentChat TriggerOpenAI Chat ModelMemory Buffer WindowEdit Fields

Blockchain DEX Screener Insights Agent

Configured with Agent, Chat Trigger, OpenAI Chat Model, Memory Buffer Window, and additional nodes. Review the connections and setup before adapting this template.

Download workflow JSONView files on GitHub ↗15 nodes · MIT
Workflow preview
TriggerWhen chat messagereceivedChat TriggerAI & modelsOpenAI Chat ModelOpenAI Chat ModelData storeWindow Buffer MemoryMemory Buffer WindowTriggerTelegram TriggerTelegram TriggerAI & modelsBlockchain DEX ScreenerInsights AgentAgentMessagingTelegramTelegramTransformAdds SessionIdEdit FieldsWeb / APIDexScreener LatestToken ProfilesTool Http RequestWeb / APIDexScreener LatestBoosted TokensTool Http RequestWeb / APIDexScreener Top TokenBoostsTool Http RequestWeb / APIDexScreener SearchPairsTool Http RequestWeb / APIDexScreener CheckOrders Paid for TokenTool Http RequestWeb / APIDexScreener Get Pairsby Chain and Pair…Tool Http RequestWeb / APIDexScreener Token PoolsTool Http RequestWeb / APIDexScreener Pairs byToken AddressTool Http Request

Node categories in this workflow

  • Trigger
  • AI & models
  • Data store
  • Messaging
  • Transform
  • Web / API

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
When chat message receivedTriggerChat TriggerSee node parameters
OpenAI Chat ModelAI & modelsOpenAI Chat ModelSee node parameters
Window Buffer MemoryData storeMemory Buffer WindowSee node parameters
Telegram TriggerTriggerTelegram TriggerSee node parameters
Blockchain DEX Screener Insights AgentAI & modelsAgentSee node parameters
TelegramMessagingTelegramSee node parameters
Adds SessionIdTransformEdit FieldsSee node parameters
DexScreener Latest Token ProfilesWeb / APITool Http RequestSee node parameters
DexScreener Latest Boosted TokensWeb / APITool Http RequestSee node parameters
DexScreener Top Token BoostsWeb / APITool Http RequestSee node parameters
DexScreener Search PairsWeb / APITool Http RequestSee node parameters
DexScreener Check Orders Paid for TokenWeb / APITool Http RequestSee node parameters
DexScreener Get Pairs by Chain and Pair AddressWeb / APITool Http RequestSee node parameters
DexScreener Token PoolsWeb / APITool Http RequestSee node parameters
DexScreener Pairs by Token AddressWeb / APITool Http RequestSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • openAiApi
  • telegramApi

Workflow notes

Blockchain DEX Screener Insights Agent

Blockchain DEX Screener Insights Agent

Purpose and structure

This folder contains the Blockchain DEX Screener Insights Agent workflow. Its executable nodes use agent, chatTrigger, lmChatOpenAi, memoryBufferWindow, set, telegram, telegramTrigger, toolHttpRequest. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

When chat message received, Telegram Trigger

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Telegram/0340_Telegram_Automation_Webhook.json MIT; preserve source notices.

More in AI & research

"Hey Siri, Ask Agent" workflow#️⃣Nostr #damus AI Powered Reporting + Gmail + Telegram(G) - Email Classification