A useful integration is not automatically a safe integration just because a provider has been chosen.
In a recent OpenClaw implementation, a licensed property-search provider was selected as the preferred next source for live inventory. The work did not stop at that decision. The provider’s public terms showed that access, lead handling, renewal, and data use had conditions that still needed confirmation. So the integration was recorded as selected, but kept disabled while the agreement, exact price, implementation method, and permission for any local data use remained unresolved.
Selection is not authorization
It is easy to treat a vendor choice as a green light to turn on a connector. That shortcut can create avoidable cost, licensing, privacy, or data-quality problems. A provider may offer a hosted search experience without permitting its records to be copied into a local directory. A sales page can describe a bundle without settling the actual charge, renewal terms, or the account that will receive leads.
“Selected” is a decision state. “Enabled” is an operational state. They should not be confused.
The control that kept the project honest
- Record the source as selected pending contract, rather than calling it live.
- Keep the connector disabled by default until commercial and technical conditions are confirmed.
- Separate hosted-search permission from permission to store, republish, or enrich source records.
- Preserve clearly labelled demonstration data instead of presenting it as live inventory.
- Require explicit approval before a paid purchase, account activation, or production import.
- Document the exact evidence needed to move from selected to enabled.
Why this matters beyond real estate data
The same pattern applies to AI tools, payment services, analytics, CRMs, and automation platforms. A connection can look technically simple while its real operating contract is incomplete. Keeping the state visible prevents a dashboard, directory, or assistant from implying that a source is live when it is not.
Good automation does not only move quickly. It makes the next safe action obvious. When an integration is waiting on authorization, the right result is a clear disabled state—not a quiet workaround or an invented claim of readiness.
