| name | lead-storage |
| description | Persist validated lead objects through write-only storage operations after Supervisor provides explicit confirmation. Use when users ask to save approved leads to Google Sheets or DB, including normalized location and priority fields. Recommended chain end: supervisor confirmation then lead-storage. Do not use for parsing, extraction, analytics, or action recommendation. |
Lead Storage
Store validated leads with strict confirmation gating.
Quick Triggers
- Save approved leads to Google Sheets.
- Persist these normalized records after confirmation.
- Commit validated leads with confirmation token.
Recommended Chain
... -> supervisor confirmation -> lead-storage
Execute Workflow
- Accept payload from Supervisor.
- Validate payload with
references/storage-input.schema.json.
- Verify
confirmation_token is present and non-empty.
- Write leads to storage through write-only interfaces.
- Preserve optional extraction/normalization/scoring metadata when present:
- extraction:
deal_type, asset_class, price_basis, area_sqft, area_basis
- record typing:
dataset_mode, record_type
- location:
city, city_canonical, locality_canonical, micro_market, location_hint
- prioritization:
urgency, priority_bucket
- Enforce idempotency by
lead_id and avoid duplicate inserts for repeated broker forwards.
