Automate Dune Analytics Reports and Get Daily Blockchain Insights
Create an AI agent that runs Dune Analytics queries, compiles data, and sends you automated reports with blockchain metrics and insights.
What You'll Build
Your AI agent will automatically pull blockchain data from Dune Analytics and deliver insights. It can:
- Run Dune queries automatically on your schedule (daily, weekly, on specific events)
- Analyze and summarize results into plain language insights highlighting key trends and changes
- Generate visual reports with charts, tables, and formatted data
- Deliver via email or Slack with actionable insights and direct links to full dashboards
Before You Start
- An Everna account (sign up at app.everna.io)
- Dune Analytics account with API access
- Dune queries or dashboards you want to automate
- Email or Slack for report delivery
How to Set It Up
Create Your Agent
Go to app.everna.io and click New Agent. Name it "Dune Report Bot" or "Blockchain Analytics Agent".
Define Your Reporting Strategy
Tell your agent which queries to run, how often, and what insights to extract. Here are three examples:
Example 1: Daily Protocol Metrics
"Every day at 9am UTC, run these 3 Dune queries: [query IDs for TVL, daily users, transaction volume]. Compare today's numbers to yesterday and last week. Send me an email with: summary of key metrics, percentage changes with up/down indicators, notable trends or anomalies, and links to full dashboards. If TVL drops more than 10% or daily users spike 50%, send an urgent Slack alert immediately."
Best for: Daily monitoring of your protocol or project
Example 2: Competitive Analysis Report
"Every Monday, run queries comparing my DEX to top 5 competitors: Uniswap, Curve, Balancer, SushiSwap, PancakeSwap. Pull metrics: weekly volume, unique traders, fees generated, market share percentage. Create a formatted table ranking all protocols. Write a 2 paragraph analysis of where we stand and what changed this week. Send via email with subject line including our rank and volume. Save all data to a Google Sheet for historical tracking."
Best for: Weekly competitive intelligence
Example 3: Event Triggered Reports
"Monitor this Dune dashboard every hour: [dashboard URL]. When you detect any of these events: new whale wallet with 100+ ETH deposits, gas prices spike above 100 gwei, or daily active addresses exceed 50k, immediately run detailed queries about that event. Generate a report explaining what happened, the scale, historical context, and potential implications. Send to #blockchain-intel Slack channel with @channel mention for visibility."
Best for: Real time monitoring with context
Connect Required Tools
Enable the tools your agent needs:
- Dune Analytics API - Run queries and fetch results (connect your API key)
- Notifications - Send reports via Email or Slack
- Spreadsheet Access - Save historical data to Google Sheets (optional)
- Web Browser - Access Dune dashboards and verify data
Launch Your Reporting Agent
Click Create Agent to deploy. Your agent will start running queries on schedule and deliver reports automatically.
Review your first few reports to ensure data accuracy and adjust formatting preferences.
Best Practices for Automated Reporting
Compare Data Over Time
Absolute numbers are less useful than trends. Always include comparisons to previous day, week, month, and year ago. This reveals what's actually changing.
Highlight Anomalies Automatically
Have your agent flag unusual movements like 20%+ changes, all time highs/lows, or values outside normal ranges. This saves you from hunting through numbers.
Include Context and Interpretation
Raw data is hard to act on. Have your agent explain what the numbers mean, why they might be changing, and what to watch next.
Keep Historical Records
Log all query results to a spreadsheet with timestamps. This creates a historical database for long term trend analysis.
Optimize Query Timing
Run queries after data is likely complete. For daily reports, run at 9-10am UTC after previous day data has fully propagated to Dune.
Common Issues and Solutions
Queries timing out or failing
Complex queries can time out. Break large queries into smaller ones. Use Dune's materialized views for frequently accessed data. Consider upgrading your Dune plan for longer query timeouts.
Data looks incorrect or outdated
Dune data can have indexing delays. Build in time buffers (run reports for previous complete day, not current day). Cross check against blockchain explorers for validation.
Reports are too long or overwhelming
Focus on key metrics only. Put detailed data in attached spreadsheets. Use executive summary format: 3-5 key takeaways at top, detailed tables below.
Missing important events between scheduled runs
Add event monitoring alongside scheduled reports. Run quick queries hourly to check for threshold breaches, then trigger detailed reports only when something significant happens.