Skip to main content

How Propexo Connect Works

Propexo Connect has six building blocks: sources, destinations, connectors, connections, streams, and records.

The Building Blocks​

Sources​

Inspection platforms, AI communications tools, maintenance systems, payments, access control, screening services, and core property platforms are all sources — the systems Propexo Connect pulls data from. When you configure a source, you select the right connector and provide credentials so the platform can authenticate and access your data.

For example, connecting an inspection or AI-leasing product as a source means providing API credentials and any account-specific parameters. Propexo Connect handles the rest — discovering what data is available, understanding the schema, and managing the extraction.

Destinations​

Your data warehouse or database is your destination — the system where extracted data lands. Destination connectors are documented under Data Warehouses in the Connector Directory. Once configured, a destination can receive data from any number of sources.

Connectors​

Every source and destination is powered by a connector — a purpose-built integration module maintained by the Propexo team. Connectors handle authentication, data discovery, and the mechanics of reading or writing data. Propexo Connect offers 127+ connectors covering the major proptech platforms, and each one receives ongoing maintenance as vendor APIs evolve.

Pipelines (Connections)​

A connection is a configured pipeline that pairs one source with one destination. It defines everything about how data moves: which data streams to include, the sync mode, the schedule, and where records land in the destination.

Streams​

Within each connection, streams represent the individual data sets being replicated. Depending on the connector, that might mean inspections and items, messages and threads, work orders and vendors, or — when you use those connectors — properties, units, leases, and charges from a core property system.

Records and Fields​

A record is a single entry within a stream — one inspection walk, one conversation, one work order, or one lease row, depending on the stream. Each record is made up of fields (the individual attributes the connector exposes for that entity).

The Sync Lifecycle​

When a pipeline runs, Propexo Connect follows a consistent sequence:

  1. Schema discovery — The source connector queries the external system to catalog available streams and their fields
  2. Extraction — Data is pulled from the source according to your configuration — every record for a full refresh, or only new and changed records for incremental syncs (where supported by the source connector)
  3. Loading — Extracted records are written to your destination according to your connection configuration

Controlling When Data Moves​

Every connection has a schedule that determines when syncs fire:

  • Cron — Run on a precise recurring cadence (e.g., every 6 hours, daily at 2 AM UTC)
  • Manual — Trigger syncs on demand from the console whenever you need fresh data

Where Data Lands​

When you configure a connection, you specify a namespace — the logical container in your destination that groups related streams. What that maps to in practice depends on the destination connector. You can also add a stream prefix so streams from different sources that share the same name stay clearly separated at the destination.

Keeping Pipelines Healthy​

Propexo Connect includes built-in mechanisms for reliability:

  • Auto-retry — Failed syncs are automatically retried, recovering from transient network or API issues without manual intervention