For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dashboard
How It WorksKnowledge BaseOnboardingVideo TutorialsPMS GuidanceAPI ReferenceRelease Notes
  • Getting Started
    • Introduction
  • Propexo API Concepts
    • Authentication
    • Custom Data Objects
    • Data Fetching Methodology
    • Deleted Records
    • Enabling Properties
    • Filtering Results
    • Integration Cloning
    • Pagination
    • Rate Limiting
    • Records Processed
    • Sorting Results
    • Sync Frequency
    • Sync Schedules
    • Write Requests
  • Webhooks
    • Webhooks Overview
    • Setting Up Webhooks in Propexo
    • Sending a Test Webhook
    • Sequencing and Data Hydration
    • Signed Payloads
Dashboard
LogoLogo
On this page
  • Overview
  • Configurations
  • Limitations
  • How To Clone
Propexo API Concepts

Integration Cloning

Was this page helpful?
Previous

Pagination

Next
Built with

Overview

Because Propexo is highly configurable at the integration level, it can be helpful to “clone” an integration’s configurations to create a new integration. This can save time and effort as part of your implementation strategy.

Configurations

The following is a list of configurations included when you clone an integration.

  • Job Schedules - This configuration defines when and how often we request data from the PMS.
  • Date Filters - This configuration controls the date range filters applied to the PMS for a given data model
  • Job Controls - This configuration defines which Propexo ETL jobs run at a more granular level. We will work with you to configure these settings the first time.
  • Custom Enum Maps - Propexo provides a default set of normalized enum values used across your entire Propexo ecosystem. However, sometimes, customers like to define custom enum mappings. We will work with you to set these for the first integration, but they can be deployed across new integrations as part of the cloning process.
  • Transform Schemas - This configuration defines how data gets mapped from the PMS to Propexo. These are standardized across the entire Propexo ecosystem but can be customized per customer and integration.

Limitations

You may only clone an integration from one PMS to the same PMS. For example, if you have a Propertyware integration, you may not clone that to a Buildium integration. It must be Propertyware to Propertyware.

You may only clone within a given environment. For example, you may not clone from a sandbox to a production environment. Cloning is limited to sandbox to sandbox or production to production.

How To Clone

You can clone an integration via the Propexo API or the Propexo Dashboard.

For the Propexo API, you can use POST /integrations endpoint and leverage the based_on_integration_id parameter. More docs can be found here

In the Propexo Dashboard, you can use the “Clone Customer” button by selecting an existing integration and clicking the ”…” menu. You can follow the visual steps below.

Propexo Integration Cloning