DealTrail 3.0
  • 1. Introduction & Vision
    • 1.1 What is DealTrail?
    • 1.2 The Tech Stack
    • 1.3 The "Amy" Persona
    • 1.4 Problem / Solution
    • 1.5: Blueprint for Autonomous Transaction Coordination
  • 2. The Memory (Supabase)
    • 2.1 Why Supabase?
    • 2.2 Supabase Setup
    • 2.3 The Schema Blueprint
  • 3. Ingestion & Routing
    • 3.0 Architecture Overview
    • 3.1 AgentMail Configuration
    • 3.2 n8n - The "Central Brain" Router
    • 3.3 The Ambiguity Protocol
  • 4. Core Workflows (n8n)
    • 4.0 Architecture Overview
    • 4.1: Workflow A: New Deal Onboarding
    • 4.2 Workflow B: Drafting Documents
  • Transaction Knowledge
    • Opening Escrow
    • Seller Process
    • Buyer Process
Powered by eniston
  1. Overview
  2. 2. The Memory (Supabase)

2. The Memory (Supabase)

  • 2.1 Why Supabase?

    Giving Amy a Brain.Imagine hiring a brilliant assistant who reads every email instantly and works 24/7, but suffers from severe short-term memory loss. Once she finishes a task, she forgets it ever happened.That is what n8n (our automation tool) is on its ...

  • 2.2 Supabase Setup

    From Zero to Database in 5 Minutes.Follow this guide exactly to provision the memory for DealTrail. We are setting up a Postgres database in the cloud that will store every deal, agent, and document reference.Step 1: Create the ProjectWe host our data in ...

  • 2.3 The Schema Blueprint

    Copy, Paste, Deploy.🚧 Developer Note: The schema below is a suggested starting point designed to get us to MVP immediately. It is not set in stone. As we build specific features (like billing or advanced document parsing), you should feel free to add col ...

© 2025 DealTrail 3.0