{ "$result_object_key": { "appointment_ids": "The matching appointments for the selected appointment type IDs and filter combination", "count": "The count of matching appointments for the selected appointment type IDs and filter combination" }}
v1
Count Appointments For Patient
Documentation for the Count Appointments For Patient action for Healthie
This field maps to the destination API filter_by_apppointment_statuses (values: Cancelled, Re-Scheduled,No-Show, Occurred,Late Cancellation) defaults to all statuses field.
{ "$result_object_key": { "appointment_ids": "The matching appointments for the selected appointment type IDs and filter combination", "count": "The count of matching appointments for the selected appointment type IDs and filter combination" }}
You can use the result of the action’s data as inputs to downstream workflow actions.Each fetch action requires a result object key to be specified which will nest the action’s result data inside the downstream data context in the Workflow.Here we demonstrate how to refer to this data using the prefix $result_object_key.
