Skip to main content
images/intakeq.svg

​
Parameters

​
Action
Parameters
{
  "$result_object_key": {
    "content_type": "application/pdf",
    "created_at": "2024-01-23T10:00:00Z",
    "file_name": "medical_report.pdf",
    "folder_id": "folder_xyz789",
    "id": "68b72563002d161fa04ced4a",
    "size_bytes": 17432
  }
}

{
  "$result_object_key": {
    "content_type": "MIME type of the file",
    "created_at": "When the file was uploaded",
    "file_name": "Name of the uploaded file",
    "folder_id": "(Optional) ID of the folder containing the file",
    "id": "Unique identifier for the uploaded file",
    "size_bytes": "Size of the file in bytes"
  }
}

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