Parameters Appointment Type ID
string (Appointment Type)
required
This field maps to the destination API appointment_type_id field.
This field maps to the destination API provider_id field.
This field maps to the destination API start_date field.
End Datetime
timing.v1.Timestamp
required
This field maps to the destination API end_date field.
This field maps to the destination API contact_type field.
This field maps to the destination API appt_loc_id field.
{ "$result_object_key" : { "provider_id" : { "id" : null , "id_type" : null }, "slots" : null } } Result Object Description
{ "$result_object_key" : { "provider_id" : { "id" : null , "id_type" : null }, "slots" : null } } Result Object Field Details 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.
ListAvailabilitySlotsResponse
Fetch Action Response Object
Description coming soon
$result_object_key.provider_id { "id" : null , "id_type" : null } provider_id.id_type
scheduling.v1.SchedulingApplication
required
Description coming soon
$result_object_key.provider_id.id_type Description coming soon
$result_object_key.provider_id.id slots
[]timing.v1.Timestamp
required
