MindBody

MindBody's platform has fueled the boom of the boutique wellness revolution and continues to foster the growth of the global wellness industry through its software, thought leadership, and unique features. DLH.io connects to MindBody to help consolidate data from this platform with other data used in an organization in order to gain a holistic view of all operations capability to make better data driven decisions.

Connector Pre-Requisites

Connecting to MindBody, you need to make sure that:

• You have administrative access to your MindBody account

Instructions (Basic Connection Setup)

Remember DLH.io securely connects to your MindBody instance by redirecting you to the MindBody portal for you to sign in via MindBody login. DLH.io does not capture or store your password/credentials.

Using the form please complete the following basic steps:

1. Enter a Name or Alias for this connection, in the Name/Alias field, that is unique from other connectors.

2. Enter in the Target Schema Prefix field, a name that will be unique in your target destination where you wish to integrate the data.

3. Enter your api key from your MindBody account in the API Key field

4. Enter your Site Id as provided by your Mindbody account in the Site Id field

5. Enter the username of an administrator in the User field

6. Enter the password credential for the user in the Password field

7. Click the Authorize Your Account button which will transport you to the MindBody login, where you will enter your account credentials.   Once your credentials are accepted you will be automatically redirected back to the DLH.io portal and you should be able to see a successful connection.

Instructions (Video)

Coming Soon...

Source Replicated Entities

The following entities are replicated by defualt to your Target Connection. These are the table names you will see in your Target Connection or available to your target integration. If you believe any entities/tables are missing please open a ticket with Customer Support:

• View a list of entities after creating a connection in DLH.io for the most up-to-date list

Data Replication Details

This section provides information on how data is replicated, at what frequency and which replication/synchronization details are worth noting from DLH.io.

Replication Definitions

The following types of replication happen between this source and your target destination cloud data warehouse of choice when a Sync Bridge runs:

• Historical Data Load (also First Time Sync)

  • Occurs during the first/initial data sync of the sync bridge pipeline and any time you need to or are requested to conduct a historical re-sync process for your data.
  • Here, DLH.io ingests all available data for the objects/tables you've selected or are available to you from the source based on your authentication access on that source.
  • This can take a relative elongated time to retrieve all data from the source and replicated to the target, as the name suggest it is retrieval all data, so if the source contains large amounts of data even in our parallel processing capability a customer could expect more than an hour for large data system. If there are any concerns that a historical load or first time sync has not completed within a reasonable amount of time please contact DLH.io Support.

• Incremental (aka Deltas) Data Load

  • After a first time synchronization/replication or a historical data load, all subsequent processes of replicating the data for a Sync Bridge (source to target) are referred to as delta or incremental loads
  • Here, DLH.io captures the latest/newest records and/or events and any changes/updates to existing records and/or events in the source connector based on the frequency set in the Sync Bridge.

Issue Handling

If any issues occur with the authorization simply return to the sources page in DLH.io, edit the source details and click the Save & Test or Authorize Your Account or Re-Authorize Account button to confirm connectivity. If any issues persist please contact our support team via the DLH.io Support Portal.