OpenSea Analytics Agent Tool (n8n Workflow) Guide

🚀 Workflow Overview

The OpenSea Analytics Agent Tool is an AI-powered NFT analytics system built using n8n. It integrates directly with OpenSea's API to fetch and analyze market data, collection stats, wallet transactions, and event logs. This tool is designed to provide real-time insights into the NFT ecosystem.

🎯 Key Features:

• Retrieve collection statistics (volume, floor price, market cap, etc.).
• Track NFT events (sales, transfers, listings, bids, redemptions).
• Monitor wallet transactions (account-specific event tracking).
• Fetch NFT-specific historical transactions by smart contract and token ID.
• Ensure API compliance, preventing invalid queries and errors.

---

🔗 Nodes & Functions

Below is a breakdown of each node in the workflow and its function.

1️⃣ Analytics Agent Brain

• Type: AI Language Model (GPT-4o Mini)
• Purpose: Processes API requests and interprets OpenSea analytics queries.

2️⃣ Analytics Agent Memory

• Type: AI Memory Buffer
• Purpose: Stores session data to maintain context for multiple queries.

3️⃣ OpenSea Get Collection Stats

• Type: API Request
• Endpoint: /api/v2/collections/{collection_slug}/stats
• Function: Fetches collection-wide statistics such as floor price, total volume, number of sales, and market cap.

4️⃣ OpenSea Get Events

• Type: API Request
• Endpoint: /api/v2/events
• Function: Retrieves NFT-related events within a given timeframe, filtered by event type (sale, transfer, listing, etc.).

5️⃣ OpenSea Get Events by Account

• Type: API Request
• Endpoint: /api/v2/events/accounts/{address}
• Function: Tracks all NFT events related to a specific wallet address.

6️⃣ OpenSea Get Events by Collection

• Type: API Request
• Endpoint: /api/v2/events/collection/{collection_slug}
• Function: Fetches the latest events for a particular NFT collection.

7️⃣ OpenSea Get Events by NFT

• Type: API Request
• Endpoint: /api/v2/events/chain/{chain}/contract/{address}/nfts/{identifier}
• Function: Retrieves all historical events for a single NFT based on blockchain, smart contract, and token ID.

---

📌 How to Use the Workflow

✅ Step 1: Input Data

• Provide the necessary parameters like collection_slug, address, event_type, chain, and identifier.

✅ Step 2: API Calls Execution

• The workflow triggers API calls based on the input and retrieves structured NFT analytics data.

✅ Step 3: Data Processing & Output

• The AI-powered agent processes responses and formats the output.
• Results can be sent to Telegram, saved in a database, or displayed in a dashboard.

---

⚠️ Common API Queries & Examples

1️⃣ Get Collection Stats

GET https://api.opensea.io/api/v2/collections/boredapeyachtclub/stats

2️⃣ Get Events (Last 24 Hours NFT Sales)

GET https://api.opensea.io/api/v2/events?event_type=sale&after=1710960000

3️⃣ Get Events by Wallet Address

GET https://api.opensea.io/api/v2/events/accounts/0x123...abc?event_type=transfer&chain=ethereum

4️⃣ Get Events by NFT

GET https://api.opensea.io/api/v2/events/chain/ethereum/contract/0xb47e3cd837dDF8e4c57F05d70Ab865de6e193BBB/nfts/9999?limit=5

---

⚡ Error Handling & Troubleshooting

| Error Code | Description | |--------------|----------------| | 200 | Success | | 400 | Bad Request (Invalid input) | | 404 | Not Found (Incorrect slug, address, or identifier) | | 500 | Server Error (OpenSea API issue) |

🔹 Fixing Common Errors

• Ensure correct collection_slug or wallet address is provided.
• Check if the blockchain name is valid (matic instead of polygon).
• If the OpenSea API is down, retry after some time.

---

🚀 Connect with Me for Support

If you need assistance, custom OpenSea insights, or automation support, feel free to connect with me on LinkedIn:

🌐 Don Jayamaha – LinkedIn
🔗 http://linkedin.com/in/donjayamahajr

OpenSea Analytics Agent Tool

Purpose and structure

This folder contains the OpenSea Analytics Agent Tool workflow. Its executable nodes use agent, executeWorkflowTrigger, lmChatOpenAi, memoryBufferWindow, 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

Workflow Input 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/Stickynote/2027_Stickynote_Executeworkflow_Automation_Webhook.json MIT; preserve source notices.