OpenSea AI-Powered Insights via Telegram
Configured with Agent, Chat Trigger, OpenAI Chat Model, Memory Buffer Window, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Transform
- AI & models
- Data store
- Subworkflow
- Messaging
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.
| Node | Category | Type | Operation |
|---|---|---|---|
| When chat message received | Trigger | Chat Trigger | See node parameters |
| Telegram Trigger | Trigger | Telegram Trigger | See node parameters |
| Adds SessionId | Transform | Edit Fields | See node parameters |
| Opensea Supervisor Brain | AI & models | OpenAI Chat Model | See node parameters |
| Opensea Supervisor Memory | Data store | Memory Buffer Window | See node parameters |
| OpenSea Analytics Agent Tool | Subworkflow | Tool Workflow | See node parameters |
| OpenSea NFT Agent Tool | Subworkflow | Tool Workflow | See node parameters |
| OpenSea Marketplace Agent Tool | Subworkflow | Tool Workflow | See node parameters |
| Telegram | Messaging | Telegram | See node parameters |
| OpenSea AI-Powered Insights Agent | AI & models | Agent | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- 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
openAiApitelegramApi
Workflow notes
OpenSea AI-Powered Insights System (n8n) - Full Integration Guide
OpenSea AI-Powered Insights System (n8n) - Full Integration Guide
🚀 System Overview
The OpenSea AI-Powered Insights System is a fully automated n8n workflow that connects multiple agent tools to deliver real-time NFT market insights via Telegram. This system consists of four interconnected workflows:
- OpenSea AI-Powered Insights via Telegram (Main Supervisor)
- OpenSea Analytics Agent Tool (Market Trends & Collection Stats)
- OpenSea Marketplace Agent Tool (Live Listings, Offers, and Orders)
- OpenSea NFT Agent Tool (Metadata, Ownership & Payment Tokens)
These agents work in sync under the Supervisor AI, which determines the appropriate agent(s) to use based on user queries. Responses are structured and sent back via Telegram for real-time insights.
🔗 System Architecture
🔹 Core Workflow: OpenSea AI-Powered Insights via Telegram
- Acts as the brain and command center.
- Receives queries from Telegram Chat.
- Determines which agent(s) should process the request.
- Aggregates and formats results.
- Sends structured responses back to the Telegram user.
🔹 Supporting Agent Tools
Each agent tool is a separate n8n workflow with a specific function:
1️⃣ OpenSea Analytics Agent → Retrieves market trends, sales history, transaction data.
2️⃣ OpenSea Marketplace Agent → Fetches NFT listings, offers, best prices, and order details.
3️⃣ OpenSea NFT Agent → Retrieves NFT metadata, ownership records, traits, and payment token data.
The Supervisor AI (Telegram Workflow) calls these agent workflows as needed.
🛠 Setup Instructions
1️⃣ Setting Up the Main Supervisor (Telegram Workflow)
- Create a Telegram Bot using BotFather.
- Copy the API Key and connect it to n8n’s Telegram Trigger Node.
- Set up the Chat Message Received Node to capture user queries.
- Configure the Session ID Node to track conversation history.
- Link the AI Supervisor Brain (GPT-4o Mini) to process messages.
- Connect it to the three agent tools using Tool Workflow Nodes.
- Send output back to Telegram using the Telegram Node.
✅ This setup enables Telegram interaction with all OpenSea agents.
2️⃣ Configuring the OpenSea Agent Tools
Each agent tool must be linked to the main workflow:
A. OpenSea Analytics Agent
- Retrieves NFT market trends & transaction history.
- Requires collection slug, wallet address, or transaction filters.
B. OpenSea Marketplace Agent
- Fetches NFT listings, offers, and orders.
- Requires collection slug, token ID, or order hash.
C. OpenSea NFT Agent
- Retrieves NFT metadata, traits, and ownership data.
- Requires wallet address, contract address, or token ID.
3️⃣ Connecting the Agents to the Main Workflow
Each Tool Workflow Node inside the Telegram Supervisor Workflow must be configured to pass the query to the correct agent tool.
Example:
- User asks: “Find the cheapest listing for Bored Ape #1234” → Marketplace Agent is activated.
- User asks: “Retrieve all NFTs owned by 0xABC...” → NFT Agent is activated.
- User asks: “Compare last 3 months’ sales volume of Azuki and Moonbirds” → Analytics Agent is activated.
🔄 **Data Flow & Execution Process**
🔄 Data Flow & Execution Process
📩 Step 1: Receiving a Query
- User sends a request via Telegram.
- The Telegram Trigger captures the message.
- The Session ID Node assigns a conversation ID.
📊 Step 2: Processing the Query
- The AI Supervisor Brain (GPT-4o Mini) interprets the request.
- It decides which agent tool should process the query.
🔗 Step 3: Activating the Correct Agent Tool
- The appropriate Tool Workflow Node is triggered (Analytics, Marketplace, or NFT Agent).
- The selected agent processes the query and fetches data from OpenSea’s API.
📤 Step 4: Sending the Response
- The response is structured by the AI Supervisor.
- The Telegram Node sends the formatted answer to the user.
✅ This ensures that all agents work together seamlessly.
🔥 Example Queries & Expected Outputs
🛒 OpenSea Marketplace Queries
| User Query | Agent Used | Expected Response | |--------------|--------------|----------------| | “Show me the 5 cheapest listings for Azuki.” | Marketplace Agent | List of Azuki NFTs with prices & links. | | “What’s the highest offer on Bored Ape #4567?” | Marketplace Agent | Highest active bid with buyer info. | | “Fetch the details of order 0x123abc...” | Marketplace Agent | Order breakdown (price, seller, expiration). |
📊 OpenSea Analytics Queries
| User Query | Agent Used | Expected Response | |--------------|--------------|----------------| | “Compare 7-day sales volume of BAYC & MAYC.” | Analytics Agent | Chart showing sales data. | | “List all transactions for CloneX in the last 24 hours.” | Analytics Agent | Table of sales & transfers. | | “Track all wallets that sold a Doodle in the last week.” | Analytics Agent | List of wallets & sold NFTs. |
🎭 OpenSea NFT Metadata Queries
| User Query | Agent Used | Expected Response | |--------------|--------------|----------------| | “Retrieve metadata for Cool Cat #7890.” | NFT Agent | NFT description, image, and attributes. | | “Which NFTs does 0x123... own on Ethereum?” | NFT Agent | List of NFTs held by the wallet. | | “Show me all NFTs from contract 0xABC...” | NFT Agent | All tokens linked to the contract. |
✅ This demonstrates how each agent provides unique insights.
⚠️ **Critical Setup Notes & Troubleshooting**
⚠️ Critical Setup Notes & Troubleshooting
🔹 1. Ensure Correct API Credentials
- Each agent must be connected to OpenSea’s API.
- Use HTTP Header Authentication with an API Key.
🔹 2. Check for Invalid Chain Names
- ❌
"polygon"is not valid → Use"matic"instead. - ✅ Only supported blockchains should be used.
🔹 3. Maintain Session Tracking
- Ensure sessionId is passed correctly between workflows.
- This prevents context loss in multi-step queries.
🔹 4. Use Pagination for Large Datasets
- For queries returning 100+ results, use the
nextparameter.
🚀 Final Thoughts
The OpenSea AI-Powered Insights System is designed for NFT investors, collectors, and analysts seeking real-time, structured market data through Telegram. By integrating multiple agent tools, it provides a powerful, automated way to analyze NFTs, transactions, and market trends.
Need Help?
🌐 Connect on LinkedIn:
🔗 http://linkedin.com/in/donjayamahajr
OpenSea AI-Powered Insights via Telegram
OpenSea AI-Powered Insights via Telegram
Purpose and structure
This folder contains the OpenSea AI-Powered Insights via Telegram workflow. Its executable nodes use agent, chatTrigger, lmChatOpenAi, memoryBufferWindow, set, telegram, telegramTrigger, toolWorkflow. 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/2004_Telegram_Stickynote_Automation_Triggered.json MIT; preserve source notices.