Skip to main content
Workflows (also called “Agents”) are pre-trained, specialized systems designed to tackle complex analytical questions using structured, expert methodologies.

What are Workflows?

Unlike general chat mode—where FlipsideAI freestyles based on your prompt—Workflows apply quasi-deterministic (predetermined) approaches to specific types of analysis. Think of Workflows as domain experts with proven playbooks:
  • TVL analysis Workflow knows exactly how to calculate, validate, and compare Total Value Locked
  • Liquidity tracking Workflow follows established methods for assessing pool depth and health
  • User cohort Workflow applies structured cohort analysis frameworks

General mode vs Workflow mode

  • General mode
  • Workflow mode
Best for:
  • Exploratory questions
  • One-off analyses
  • Flexible, conversational interaction
How it works:
  • FlipsideAI interprets your question
  • Generates a plan on the fly
  • Adapts based on results
Example: “Show me Uniswap activity on Arbitrum”
Running the same question in general mode vs Workflow mode will give you different results—by design. Workflows are structured and methodical; general mode is flexible and adaptive.

Using Workflows

Automatic detection

FlipsideAI automatically detects when your question matches a Workflow:
You: "Analyze TVL trends for Aave vs Compound over Q1 2024"

FlipsideAI: Using workflow: TVL comparative analysis
[Applies structured TVL calculation and comparison methodology]
You’ll see “Using workflow: [name]” when a Workflow is active.

Manual selection

Use the @ symbol to browse and manually select Workflows:
1

Type @

In the chat box, type @ to open the selector
2

Browse Workflows

Scroll through available Workflows and datasets
3

Select one or more

Click to add Workflows to your prompt
4

Ask your question

Complete your prompt with the specific question
Example:
@TVL-Analysis Compare Aave and Compound over the past quarter

Common Workflows

What it does:
  • Calculates Total Value Locked using consistent methodology
  • Handles multi-asset pools and LP tokens correctly
  • Compares across protocols or time periods
  • Validates against external sources (e.g., DeFiLlama)
Best for:
  • Protocol health assessments
  • Competitive comparisons
  • Trend analysis over time
What it does:
  • Measures liquidity depth and distribution
  • Tracks liquidity providers and concentration
  • Analyzes liquidity migration patterns
  • Assesses pool health and sustainability
Best for:
  • DEX pool analysis
  • Liquidity provider behavior
  • Risk assessment for traders
What it does:
  • Segments users by first interaction date
  • Tracks retention and behavior over time
  • Compares cohorts side-by-side
  • Identifies power users vs casual users
Best for:
  • Protocol growth analysis
  • User retention studies
  • Product-market fit assessments
What it does:
  • Identifies top holders and concentration
  • Tracks holder behavior (accumulation vs distribution)
  • Flags potential risks (whale movements, centralization)
  • Analyzes holder overlap across tokens
Best for:
  • Tokenomics research
  • Risk assessments
  • Airdrop or incentive targeting
What it does:
  • Tracks cross-chain asset flows
  • Identifies bridge users and patterns
  • Compares bridge volumes and market share
  • Analyzes net inflows/outflows by chain
Best for:
  • Cross-chain ecosystem studies
  • Chain growth comparisons
  • Bridge risk assessments

When to use Workflows

✅ Use Workflows when:

  • You need consistent, reproducible methodology
  • The analysis is complex and multi-step (e.g., cohort retention with multiple metrics)
  • You’re comparing entities and want apples-to-apples analysis
  • You want expert-level approaches without specifying every step
  • You’re running recurring analyses (monthly reports, protocol monitoring)

❌ Don’t use Workflows when:

  • You’re doing quick, exploratory research
  • Your question is highly specific or unusual (Workflows may constrain the approach)
  • You want maximum flexibility in how the analysis is structured
  • You’re testing hypotheses that don’t fit standard frameworks

Requesting new Workflows

Don’t see a Workflow for your use case? Request one.
Workflow requests are reviewed and built by the Flipside team. If there’s a common analytical pattern you run repeatedly, we want to build a Workflow for it.
What to include in your request:
  1. Use case description: What problem are you solving?
  2. Analytical steps: What’s the methodology you’d like codified?
  3. Frequency: How often would you use this Workflow?
  4. Example questions: What prompts should trigger this Workflow?

Pro tips

Use Rules to customize Workflow output:
  • Rules control how results are presented
  • Workflows control what analysis is performed
Example: Use TVL Workflow with a “Twitter-ready visuals” Rule for polished charts.
If a Workflow is triggered but you want general mode instead:
"Analyze Aave TVL, but don't use the TVL Workflow—I want a custom approach"
Workflows are transparent. Ask:
  • “What methodology did you use?”
  • “Why did you calculate it this way?”
  • “Can you show me the step-by-step logic?”
Workflow results can be a starting point:
  1. Let the Workflow run its structured analysis
  2. Review the results
  3. Ask follow-up questions to dig deeper or explore tangents
The Workflow handles the foundation; you explore from there.

Understanding Workflow outputs

When a Workflow runs, you’ll see:
  1. Workflow name: “Using workflow: [name]”
  2. Structured analysis: Results organized according to the Workflow’s methodology
  3. Flipside Data boxes: Queries used to generate results (fully transparent)
  4. Artifacts or reports: Formatted outputs (charts, tables, summaries)
Unlike general mode, Workflows follow a predictable structure—making them ideal for recurring analyses or comparisons.

Next steps