Database Mappings Table

The plugin uses a custom table to maintain the link between WordPress and Zoom. This prevents unnecessary API requests by caching the meeting details locally.

📋 Table Name: `wp_kc_appointment_zoom_mappings`

Column	Type	Description
`id`	`bigint`	Primary Key (Auto Increment).
`appointment_id`	`bigint`	ID of the KiviCare Appointment.
`zoom_id`	`varchar(191)`	The raw ID for the meeting in Zoom.
`zoom_uuid`	`varchar(191)`	The unique UUID for the specific meeting instance.
`start_url`	`longtext`	The host-only link used by the Doctor.
`join_url`	`longtext`	The attendee link used by the Patient.
`password`	`varchar(191)`	The meeting passcode.
`created_at`	`datetime`	When the mapping was created.

🛠️ Accessing Data Programmatically

Developers can use the KCTAppointmentZoomMapping model to retrieve data:

use KCTApp\models\KCTAppointmentZoomMapping;

// Find mapping for a specific appointment
$mapping = KCTAppointmentZoomMapping::where('appointment_id', $id)->first();

if($mapping) {
    echo "Zoom Join URL: " . $mapping->join_url;
}

🗑️ Data Cleanup

When an appointment is deleted in KiviCare, the plugin hooks into the deletion event to:

Cancel the meeting on Zoom using the zoom_id.
Delete the corresponding row from this mapping table.

Next: Plugin REST API Endpoints

Previous
Zoom API Usage & Scopes

Next Plugin REST API Endpoints

Database Mappings Table

📋 Table Name: wp_kc_appointment_zoom_mappings

🛠️ Accessing Data Programmatically

🗑️ Data Cleanup

Suggestions & Improvements Cancel

📋 Table Name: `wp_kc_appointment_zoom_mappings`