Pipeline Basics
A pipeline in Propexo Connect — called a connection — is the central unit of data movement. It pairs one source connector with one destination connector and defines everything about how data from that operational system flows into your analytical environment.
What a Connection Controls
Every connection specifies:
| Setting | What It Determines |
|---|---|
| Stream and field selection | Which data sets and fields to replicate (e.g., inspections, conversations, work orders, or core lease entities — depending on the connector) |
| Sync mode | How data is read from the source and written to the destination |
| Sync schedule | When and how often syncs run |
| Destination namespace | Where replicated data is organized in your destination |
Each execution of a connection is called a sync. Syncs can run on an automated cron schedule or be triggered manually from the console.
Building Your First Pipeline
Once you've configured a source and destination, creating a pipeline takes a few steps:
- Create a connection — Pair your source (for example an inspection or AI communications connector) with your destination
- Select streams — Choose which data sets to replicate. For an inspection or messaging source, that might include walks, findings, threads, or leads; for a core property connector, it might include properties, units, leases, tenants, and charges.
- Configure sync behavior — Pick a sync mode for each stream and set a schedule
- Set the namespace — Define how replicated data is grouped in your destination
- Activate — Save the connection and let the first sync run
Streams
Streams are the individual data sets within a connection. Each 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—what you select from a source and configure in a connection—not as a fixed promise about a particular table, file, or object layout in every destination. How a stream maps into your systems depends on the connectors and options you use.
You can configure streams individually within a connection for fine-grained control — selecting specific fields, choosing different sync modes per stream, or excluding streams you don't need.
Destination Namespaces
A namespace groups related streams under a common container in your destination. The exact representation depends on your destination connector and how Connect models that system.
You can also add a stream prefix when multiple sources expose the same stream name, so they stay clearly separated at the destination — for example, disambiguating two inspection tools or an inspection feed and a messaging feed that both use a generic name such as locations.