Integrations
Connected to the systems you already run.
Soluna sits between the voice conversation and your clinic's software through a secure automation layer. We assess every integration before we promise it.
How the pieces fit together.
A single, auditable path from the call to your systems and your team.
Retell AI
Natural voice conversation, in Spanish and English.
Secure automation layer
Soluna on n8n. Authenticated, tenant-specific, logged.
CRM
Clean records and callbacks
Booking system
Availability and requests
Telephony
Forwarding and transfer
Your staff
Human handoff and confirmation
This is a general architecture. The exact connections depend on what your clinic uses and what each provider's API allows.
What we connect, and how.
Integration assessment
We start by reviewing your current telephony, CRM and scheduling, and what each supports.
Supported APIs
We connect through documented, authorized APIs rather than fragile workarounds.
Authentication
Each clinic uses its own credentials, scoped to only what the workflow needs.
Calendar connections
Where a scheduling provider allows it, we read availability and create requests or bookings.
CRM connectivity
Inquiries, callbacks and outcomes are written back to your system as structured records.
Practice management software
We assess medical practice software case by case; capability depends on the provider's API.
Phone forwarding
Calls route to Soluna after hours, on overflow, or on a dedicated line, as you prefer.
Human-confirmed fallback
Where direct booking is not supported, Soluna creates a request and a person confirms.
We won't claim a connection we haven't verified.
We do not list providers as natively supported or officially partnered unless that has been confirmed for your setup. If an integration isn't possible, we tell you, and we design the safest workflow around it.
Check your compatibility
Tell us what your clinic runs today and we'll come back with an honest technical assessment.