Tebra (Kareo) SOAP API ↔ Google Calendar Sync — Appointment Mirror + Busy-Block (fixed-scope build)

I run a small solo medical practice using Tebra (formerly Kareo) as my EHR/practice management system. I need two small, strictly one-directional syncs built against Tebra's SOAP Web Services API (v2.1). I already have the API Customer Key in hand — work can start immediately. Full build brief attached with acceptance criteria; please read it before quoting. Component A — Appointment mirror (Tebra → Google): Poll the Tebra Web Services API (SOAP 2.1, GetAppointments) on a schedule — every 60–90 minutes during business hours, once overnight Create/update/delete matching events on a dedicated Google sub-calendar Event titles: patient name + visit type + telehealth/office tag; configurable content rules per the attached brief (HIPAA-conscious — full spec in brief) Tebra AppointmentID stored in event extended properties as the match key Cancelled/no-show appointments logged to a Google Sheet Component B — Busy-block sync (Google → Tebra): Read Busy events from one designated personal Google calendar Create corresponding blocked/non-bookable time in Tebra so online booking and my AI phone receptionist can't schedule patients over personal commitments Blocks only — this component must never create, modify, or cancel a patient appointment Generic block labels only; no Google event content copied into Tebra All-day Busy events block the full clinical day; configurable travel buffer on timed blocks Failure bias: when uncertain, leave blocks in place Both: graceful failure (log and retry next cycle, never duplicate), idempotent runs, no sync loops between the two components, heartbeat email alert if the sync stops running, key settings client-adjustable via config, delivered as an n8n workflow (preferred) or scheduled Google Cloud Function, with a README covering operation and how to disable each component independently. Modular/extensible construction per the brief — everything runs in my accounts, source/workflow export delivered. I will provide: Tebra API customer key + a dedicated API user login (System Admin role) Tebra's official API Integration Technical Guide (PDF) Access to create OAuth/service-account credentials in my Google Workspace (I am the super admin), or I'll create them per your instructions The target Google sub-calendar and cancellation-log Sheet Required experience: SOAP/XML web services (Tebra/Kareo API experience is a strong plus — mention it in your proposal) Google Calendar API Comfort with healthcare data handling; you will sign a simple confidentiality agreement. You will only see appointment metadata, not clinical records. Not in scope (do not quote for these): Creating/modifying patient appointments in Tebra from Google (blocks only) Bidirectional conflict resolution Syncing any other data (patients, charges, notes) Ongoing monthly maintenance retainer After successful delivery, I plan to commission several small additional workflows on the same infrastructure (patient recall reporting, call-capture automation, data exports) — fixed quotes will be requested from the delivering developer first.