Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.morf.health/docs/llms.txt

Use this file to discover all available pages before exploring further.

images/acuity.svg

​
Parameters

​
Action
Parameters
{
  "$result_object_key": {
    "active": true,
    "calendar_ids": [
      "7568038"
    ],
    "category": "Consultations",
    "description": "First consultation with a provider",
    "id": "38932233",
    "length_minutes": 30,
    "minutes_padding_after": 5,
    "minutes_padding_before": 5,
    "name": "Initial Visit",
    "private": false,
    "scheduling_url": "https://app.acuityscheduling.com/schedule.php?owner=27553604"
  }
}

{
  "$result_object_key": {
    "active": "Whether the appointment type is deleted (true = active, false = deleted)",
    "calendar_ids": "List of calendar IDs associated with this appointment type",
    "category": "The category of the appointment type",
    "description": "Optional description of the appointment type",
    "id": "Unique identifier for the appointment type",
    "length_minutes": "Duration of the appointment type in minutes",
    "minutes_padding_after": "The time padding after the appointment",
    "minutes_padding_before": "The time padding before the appointment",
    "name": "The name of the appointment type",
    "private": "Whether the appointment type is private",
    "scheduling_url": "URL for scheduling this appointment type"
  }
}

​
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.
​
AppointmentType
Fetch Action Response Object