AI & autonomy
Integration inventory
A maintained register of connected systems, their purpose, data access, authority, owner, dependencies, and offboarding path.
Glossary
AI & autonomy
Primary references on this page:
·
Buildium Open API documentationAn integration inventory is the operating map of every outside system connected to a property-management account. It answers what is connected, why it exists, what it reads or changes, which properties it covers, who owns it, and how access will be removed. A marketplace badge or browser list does not provide that accountability.
For each connection, preserve the provider and product, environment, authentication method, scopes, data sent and received, write authority, webhook or scheduled jobs, system of record, support contact, last review, known failure path, and offboarding steps. Reference secrets by vault location rather than placing credentials in the inventory.
A duplex owner discovers that a former leasing add-on still receives applicant updates even though the subscription is no longer used. The inventory reveals the old webhook, its API key owner, and the deletion/export procedure. Without it, cancelling the invoice might leave data access or an active callback behind.
Review the register when adding a connection, changing scope, migrating systems, rotating credentials, or ending service. Ask whether the product can export a current connection list and whether disabling an integration also stops tokens, jobs, webhooks, and retained data. If ownership is “whoever set it up,” the control is fragile.
Minimum register fields
Capture purpose, business owner, technical contact, properties/accounts, permissions, data classes, write effects, schedule or subscriptions, review date, incident route, and removal evidence.
Use it as a decision tool
Before approving a new AI assistant or reporting add-on, compare its requested data and authority with existing connections. The register can reveal duplicate access, conflicting writers, and a missing system-of-record decision.
Inventory fields and lifecycle
Record workflow, systems, objects, property scope, owner, authentication, permissions, write authority, trigger, retries, monitoring, fallback, and verification. A vendor name does not reveal effects.
Use propose, review, configure, test, release, monitor, change, suspend, and retire. Retirement disables credentials, webhooks, jobs, and assumptions.
Credential-change scenario and checklist
Example: after bank reauthorization, a healthy connection returns different accounts. Compare identities, types, currencies, ownership, continuity, and mappings before automation resumes.