Module 13 · Week 3Weave Integrations Academy
SyncApp Code Flow & Creating a New Integration
From Service Start to Entity Implementation — A Complete Walkthrough
Module Overview
This five-part module is the most technically deep series in the entire onboarding program. It walks through the SyncApp codebase end-to-end: how the service starts, how sync functions are invoked, how the batch syncer locks and loops, how to create a new integration folder with HTTP client and APIs, what entities must be implemented for each data type, and how full/partial sync and push types work in practice.
Why This Module Matters
This is the core of your day-to-day work as an Integrations engineer. Every new PMS integration follows exactly this code structure. Understanding it deeply — not just conceptually but in the actual Go code — is what makes you productive on your first real ticket.
Learning Goals
- Trace the SyncApp startup sequence from main() through service start
- Understand how RunSyncFunctions loops over registered sync functions
- Explain what the singular instance check does and why it prevents concurrent runs
- Know the minimum files to create for a new integration: folder, HTTP client, API, entities
- Implement sync methods for patients, appointments, client locations, providers, and appointment types
- Understand push types and when to use them instead of polling
Lessons
13.1Code Flow Part 1 — Service Start & Entry Point~8 min13.2Code Flow Part 2 — RunSyncFunctions & Batch Syncer Lock~8 min13.3Code Flow Part 3 — Integration Structure & Scheduler Config~9 min13.4Code Flow Part 4 — Entity Implementation (Patients, Appointments, Locations, Providers)~10 min13.5Code Flow Part 5 — HTTP Client, APIs, Push Types & Full/Partial Sync~10 min