Mindbody setup

Liftrr reads from Mindbody. It never writes. Connection happens through the Mindbody integration page on the tenant and the SaaS admin sync console.

Credentials

• Mindbody API key and partner secret are configured via environment variables, never in the UI.
• Site IDs are recorded per integration and masked in cross-tenant views.
• If credentials are missing, the integration page shows a clear "Not connected" state.

Safe test sync

Always start with the safe test sync. It limits the pull to 3 entities (locations, programs, services), 1 page each, max 25 rows. It uses no historical window and never touches the cost-sensitive contracts endpoint. The action requires an explicit confirmation in the UI.

Dry run vs real run

• Dry run: fetches and counts but writes no raw records and never promotes the integration to "connected".
• Real run: writes raw records and, on success, promotes the integration to "connected".

Pause, resume, clear error

Use the pause and resume controls if you need to stop a tenant temporarily. Use clear error after fixing an upstream problem so the status badge resets.

Webhook refetch

Webhook refetch is disabled by default via an environment kill switch. Enable explicitly and only after credentials are verified for a tenant.

Things Liftrr does not do

• Liftrr does not write back to Mindbody.
• Liftrr does not impersonate users in Mindbody.
• Liftrr does not store full credentials in logs or audit rows; error strings are redacted before persistence.