{ "$result_object_key": { "access": "The access level of the file", "created_at": "The timestamp when the file was created", "extension": "The file extension", "id": "The unique identifier for the file", "name": "The name of the file", "path": "The path to the file", "updated_at": "The timestamp when the file was updated", "url": "The URL of the file" }}
v1
Create File
Documentation for the Create File action for Hubspot
{ "$result_object_key": { "access": "The access level of the file", "created_at": "The timestamp when the file was created", "extension": "The file extension", "id": "The unique identifier for the file", "name": "The name of the file", "path": "The path to the file", "updated_at": "The timestamp when the file was updated", "url": "The URL of the file" }}
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.