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. 3. Ingestion & Routing

3. Ingestion & Routing

  • 3.0 Architecture Overview

    Building the Traffic Controller.In a standard SaaS app, users log in to a specific workspace, so we always know which "deal" they are working on. In DealTrail, everyone emails one address: tc@dealtrail.com.This creates a Routing Problem. If a Lender email ...

  • 3.1 AgentMail Configuration

    Setting up the Ears.We use AgentMail.to because it parses messy emails into clean JSON for us.Access AgentMail Documentation here: https://docs.agentmail.to/welcomeStep 1: Provision the InboxLog in to your AgentMail Dashboard.Create a new Organization: De ...

  • 3.2 n8n - The "Central Brain" Router

    The Logic that sorts the mail.This is the most critical logic in the entire system. It lives inside the n8n Ingestion Workflow.The Logic FlowWhen an email arrives, we run this 3-step check:Check 1: Who is the Sender? (The Stakeholder Match)Query: Search S ...

  • 3.3 The Ambiguity Protocol

    What happens when Amy is confused?If the Router (Article 3.2) cannot determine the deal with >90% confidence, we DO NOT GUESS. Guessing leads to filing the wrong contract in the wrong SkySlope file.Instead, we trigger the Ambiguity Protocol.The "Clarif ...

© 2025 DealTrail 3.0