Skip to main content
Sync events fire when Cobalt detects changes that occurred directly in your EHR system. These keep you informed about activities your staff performed in the EHR itself — appointments scheduled, patient information updated, and statuses changed.
appointment.created and appointment.updated also fire as Operation Events when triggered by an RPA action Cobalt performed. The event types are the same; the trigger differs.

Payload Envelope

Every sync event uses this envelope:

Appointment Events

Triggered when EHR staff create an appointment in your EHR (detected by Cobalt’s sync).Payload Example:
Data Fields:
Triggered when EHR staff update an appointment in your EHR (detected by Cobalt’s sync).Payload Example:
Data Fields:
Triggered when an appointment’s status changes in your EHR system.Payload Example:
Data Fields:

Patient Events

Triggered when patient information is updated in your EHR system.Payload Example:
Data Fields:

Claim Events

Triggered when a new claim is detected in your EHR (detected by Cobalt’s sync).Payload Example:
Data Fields:
Triggered when a synced claim changes in your EHR. Only fires when a header field actually changed (for example a status, payment, or balance update), so unchanged claims re-seen during a sync do not emit an event.Payload Example:
Data Fields:The full claim object (same fields as claim.created) plus: