Integrations
Seamless aged care integration with your existing systems
Zuji is a platform designed to deliver seamless aged care integration that extends the capabilities of your existing software, rather than replacing it. Whether you use a custom enterprise stack or a standard CRM, Zuji automates the conversation and pushes the results back where they belong—in your existing systems.
Integration Philosophy: Aged Care Integration Without Silos
We understand the “swivel chair” problem. You don’t want your team logging into a separate portal. Zuji provides the robust aged care integration you need to operate on a “headless” architecture principle.
Zuji operates on a “headless” architecture principle. While we provide a user interface for configuration, 100% of Zuji’s core functionality – from initiating calls to retrieving transcripts – is accessible via our RESTful API. This allows you to trigger AI agents programmatically based on events in your own software.
- Eliminate Data Silos: Client data stays in your existing system. Zuji only holds what it needs to execute a given call.
- Automated Triggers: Send a “Welcome Call” automatically when a new client is added to your system.
- Real-time Updates: Webhooks push call outcomes (e.g., “Escalation Required”) back to your system instantly, instead of, or in addition to Zuji’s built in email and sms notification capabilities.
The integration lifecycle
Zuji supports two primary integration methods: Full API Integration for automated workflows and Bulk CSV Upload for batch campaigns.
1. Ingest (data in)
Your system pushes the necessary call context to Zuji. You can trigger a single interaction or a bulk campaign.
2. Orchestrate (the call)
Zuji’s AI agent executes the call using the rules and scripts you have defined.
3. Sync (data out)
Once the call is complete, Zuji returns the structured data to you.
Architecture & Security
Zuji is architected for the strict requirements of the Australian aged care sector.
| Feature | Specification |
| Data Residency | Australia Only. All persistent data (client profiles, recordings, transcripts) is stored in data centers located in Australia. |
| API Standard | RESTful API delivering JSON payloads. |
| Authentication | Secure token-based authentication for all API requests. |
Visit our Trust Centre to learn more.
Developer resources
Tools for your technical team
We provide the documentation and environments your technology team needs to build a proof-of-concept in days, not months.
- Swagger/OpenAPI Spec: Complete definition of all endpoints, inputs, and outputs.
- Sandbox Environment: Test your triggers and webhooks without calling real clients.
- Webhooks Guide: Detailed examples of payload structures.
Non-Technical? No Problem. If you don’t have an in-house development team, Zuji works out of the box. You can manage your campaigns using our secure web portal and simple CSV imports/exports.
FAQ for technologists
Q: Can we trigger calls based on logic in our care platform?
A: Yes. For example, if a care worker marks a visit as “Cancelled” in your scheduling app, your system can automatically hit the Zuji API to trigger a “Visit Reschedule” call to a client.
Q: How do we handle authentication?
A: Zuji uses standard secure API key authentication. You can manage and revoke keys via the Zuji administrative dashboard.
Q: What format is the data returned in?
A: Data is returned as structured JSON. You can extract specific fields (e.g., consent_confirmed) to map directly to fields in your database.
Q: Does Zuji replace our existing telephony provider?
A: No. Zuji acts as an agent. We handle the telephony orchestration for the AI calls we make, but we do not replace your inbound/outbound desk phones or support lines.
Ready to integrate?
Get your API key and start testing today.