{
  "for_llm": "This page documents ONE automation inside The Makenzie House's Sales & Booking System. To assess it: read the visible tabs, then use this manifest. You can answer what is safe to change (change_policy), what breaks if a 'red' item changes, how it connects to sibling pages (edges), and its known issues. Sibling pages live alongside this one.",
  "system": "Sales & Booking System",
  "unit": {
    "index": 1,
    "of": 6,
    "node": "New Dubsado Inquiries \u00bb Push to Airtable"
  },
  "platform": "make.com",
  "scenario": {
    "id": 1648846,
    "team": 624531,
    "zone": "us2",
    "name": "New Dubsado Inquiry >> Push To Airtable",
    "modules": 90
  },
  "trigger": {
    "type": "mailhook",
    "registered_to": "Dubsado inquiry notification email"
  },
  "reads": [
    {
      "airtable": "Leads",
      "why": "search by email on the Tour Booking Only route, to avoid creating a duplicate Lead"
    }
  ],
  "writes": [
    {
      "airtable": "Leads",
      "why": "create one Lead per inquiry, on every route"
    },
    {
      "airtable": "Tours (Private)",
      "why": "create a tour record, Tour Booking Only route only"
    }
  ],
  "notifies": [
    {
      "slack": "C08PY7GLU95"
    }
  ],
  "edges": {
    "upstream": [],
    "downstream": [
      {
        "node": "New Lead \u00bb Send First Message",
        "scenario": 5607012,
        "unit": 2,
        "via": "new Lead record in Airtable"
      }
    ]
  },
  "capabilities": [
    "Catches Dubsado's inquiry notification email via mail hook and routes it by subject line into 6 inquiry types (Wedding, Event Booking, Photoshoot Booking, CH Pop-Up, Wellness, Tour Booking Only)",
    "Extracts every form field per inquiry type via regex parsers (name, email, phone, guests, booking/requested dates, referral source, budget, pets, and more depending on route)",
    "Creates a Lead in Airtable for every inquiry and posts the lead name + link to your team's Slack channel",
    "On Tour Booking Only, searches Leads by email first to avoid duplicating an existing Lead, then creates a linked Tours (Private) record"
  ],
  "boundaries": [
    "Only reacts to Dubsado's notification email arriving at the mail hook \u2014 does not poll Dubsado or read inquiries any other way",
    "Only extracts fields the regex patterns are built for; a form field Dubsado adds later won't appear on the Lead until a parser is added for it",
    "Does not send the first message to the lead (that's unit 02) or manage anything downstream of Lead creation"
  ],
  "change_policy": {
    "green": [
      "slack message wording",
      "which slack channel a route posts to"
    ],
    "amber": [
      "adding a field to an existing route (needs a new regex + Airtable mapping, test after)",
      "which Airtable field a parsed value maps to"
    ],
    "red": [
      "the Dubsado notification-email / mail-hook setting",
      "the subject-line filters per route",
      "the regex parsers themselves",
      "the Tour Booking Only search-by-email step"
    ]
  },
  "known_issues": [
    "Field coverage differs by inquiry type because the underlying Dubsado forms differ \u2014 a blank Lead field is often expected, not an error",
    "Regex parsers are matched to today's exact Dubsado email wording; a Dubsado template change could silently break field extraction"
  ],
  "recovery": {
    "blueprint_backup": "build/backups/bp_1648846.json"
  }
}