Basics of New Integration Implementation
Why This Matters
When you're assigned your first new integration ticket, you need to know exactly which files to touch and in what order. This lesson gives you the checklist for adding a new PMS integration to sync-app-support.
What You'll Learn
- The provisioner list and how it's populated: the listProviders map and addProvisioner calls
- register.go: the file where all provisioner registrations live
- The minimum files to create for a new integration in sync-app-support
- How to implement each required method on the provisioner interface for a new PMS
- The integration between sync-app-support and sync-app-authentication for new integrations
Watch Video
Lesson Summary
When implementing a new integration in sync-app-support, start with register.go — add a call to addProvisioner with your new PMS's provisioner instance. Then implement the provisioner interface methods: Name (return the PMS name), Metadata (define required credential fields with types), Steps (document the setup steps), and Provision (implement validate → create data source → add settings → spin up). Look at an existing integration (e.g., DentalEMR) as a reference. All of these are with respect to sync-app-support; the SyncApp data fetching code itself lives in a separate repository.