The Role of Integrations at Weave
Why This Matters
Before writing a single line of code, you need to understand what the Integrations team actually does and why it exists. This is the first video every new Integrations engineer should watch — it explains the purpose, scope, and mechanics of integrations in plain terms. Everything else in this academy builds on this foundation.
What You'll Learn
- What integrations are: bridges between a Practice Management System (PMS) and Weave
- Why integrations are bidirectional — not just data fetching, but writing back to the PMS too
- Why Weave would be just a basic communication platform without integrations
- How the team maintains, repairs, and updates these bridges over time
- How raw PMS data is transformed into a standardised JSON format all Weave teams consume
- The difference between Cloud PMS (API-based) and On-Prem PMS (local SQL on Windows) architectures
Watch Video
Lesson Summary
Integrations are the bridges between a customer's Practice Management Software (PMS) and the Weave platform. They are bidirectional — pulling data from the PMS into Weave, and also writing data back to the PMS (such as patient updates or appointment changes). Without integrations, Weave would only function as a basic communication tool. It is integrations that unlock features for other Weave teams — messages, payments, forms — by supplying them with accurate patient and appointment data. The team is also responsible for maintaining these bridges through API version changes, authentication updates, and customer-specific issues. Because different PMS systems store data in different formats, integrations transform raw PMS data (patient records, appointments, pet data) into a single standardised JSON format that all Weave teams can consume. The approach differs by PMS type: cloud PMSs expose web APIs; on-prem legacy PMSs store data in a local SQL database on the customer's Windows machine, requiring the sync application to run directly on that machine.