Core Concepts
Propexo Connect is a data movement platform that replicates data from the specialized software you run every day — inspections, AI-powered leasing and resident comms, maintenance platforms, payments, access control, and the rest of your proptech stack — into analytical destinations. Core property systems are supported too when you need that data in the warehouse. You control what flows, how often it syncs, and how it lands in the target system.
This page covers the foundational concepts you'll encounter when working with Propexo Connect.
Source
A source is the system you pull data from — often an operational tool such as HappyCo, EliseAI, or another vendor in your connector catalog, and sometimes a database, API, file system, or core property system of record. When you configure a source, you provide the credentials and parameters the connector needs to access your data: authentication details, date ranges, filters, or other extraction criteria. The required fields vary by connector.
Destination
A destination is where your extracted data is delivered — typically a cloud data warehouse or database. Which systems are available depends on your account; see Data Warehouses in the Connector Directory or the Propexo Connect Marketplace for current destination connectors.
Connector
A connector is a pre-built integration module that knows how to communicate with a specific source or destination. It encapsulates the protocol details, authentication requirements, request structure, and response parsing logic for a given system. Every source and destination in Propexo Connect is powered by a connector.
Connection
A connection pairs a configured source with a configured destination to form an automated data pipeline. It defines the complete replication behavior: which data to move, how to move it, and when.
Configuring a connection involves the following parameters:
| Parameter | Description |
|---|---|
| Stream and Field Selection | Which data entities and fields to replicate |
| Sync Mode | How data is read from the source and written to the destination |
| Sync Schedule | When and how often syncs are triggered |
| Destination Namespace and Stream Prefix | Where replicated data is written within the destination |
Stream
A stream represents a discrete group of related records — the fundamental unit of data organization in a pipeline. Propexo Connect uses stream for that unit of data you select and configure in a connection, not as a fixed mapping to a particular storage shape at every destination. How streams appear in your systems depends on the connectors and options you use.
Record
A record is a single data entry within a stream — one row in a table, one line in a file, or one object returned by an API call. Each record typically represents a distinct entity such as an inspection, a conversation, a work order, a lease, or a transaction, depending on the stream.
Field
A field is an individual attribute within a record. In a database context, this corresponds to a column. In an API response, it maps to a key-value pair within the returned object.
Sync Schedule
Propexo Connect offers three scheduling options for triggering syncs:
- CRON — Define a precise schedule using a CRON expression for fine-grained timing control.
- Manual — Trigger syncs on demand through the UI or API.
Destination Namespace
A namespace determines where data is organized within your destination. It groups related streams under a common logical container; the concrete meaning depends on your destination connector and configuration.
Sync Mode
A sync mode controls how Propexo Connect reads data from a source and writes it to a destination. Different sync modes determine whether the destination receives a complete data replacement on each run or only new and changed records.
Auto-Retry
To minimize manual intervention and keep pipelines running reliably, Propexo Connect automatically retries failed syncs. If a sync encounters a transient error, the platform re-attempts the operation without requiring you to take action.