{ "$result_object_key": { "archived": "Whether the ticket was archived", "archived_at": "When the ticket was archived", "associated_companies": { "id": "ID", "type": "Type (label) of the association" }, "associated_contact_id": "The ID of the associated contact, or the first associated contact if there are multiple", "associated_contacts": { "id": "ID", "type": "Type (label) of the association" }, "associated_deals": { "id": "ID", "type": "Type (label) of the association" }, "created_at": "When the ticket was created", "id": "ID", "pipeline_id": "The ID of the pipeline the ticket is associated with", "properties": { "key": null, "value": null }, "recently_updated_property_names": "The properties that were updated for a webhook event triggering this event payload to be created", "updated_at": "When the ticket was updated" }}
v1
Create Ticket
Documentation for the Create Ticket action for Hubspot
{ "$result_object_key": { "archived": "Whether the ticket was archived", "archived_at": "When the ticket was archived", "associated_companies": { "id": "ID", "type": "Type (label) of the association" }, "associated_contact_id": "The ID of the associated contact, or the first associated contact if there are multiple", "associated_contacts": { "id": "ID", "type": "Type (label) of the association" }, "associated_deals": { "id": "ID", "type": "Type (label) of the association" }, "created_at": "When the ticket was created", "id": "ID", "pipeline_id": "The ID of the pipeline the ticket is associated with", "properties": { "key": null, "value": null }, "recently_updated_property_names": "The properties that were updated for a webhook event triggering this event payload to be created", "updated_at": "When the ticket was updated" }}
{ "$result_object_key": { "archived": "Whether the ticket was archived", "archived_at": "When the ticket was archived", "associated_companies": { "id": "ID", "type": "Type (label) of the association" }, "associated_contact_id": "The ID of the associated contact, or the first associated contact if there are multiple", "associated_contacts": { "id": "ID", "type": "Type (label) of the association" }, "associated_deals": { "id": "ID", "type": "Type (label) of the association" }, "created_at": "When the ticket was created", "id": "ID", "pipeline_id": "The ID of the pipeline the ticket is associated with", "properties": { "key": null, "value": null }, "recently_updated_property_names": "The properties that were updated for a webhook event triggering this event payload to be created", "updated_at": "When the ticket was updated" }}
You can use the result of the action’s data as inputs to downstream workflow actions.Each fetch action requires an object name, which nests the action’s result data inside the downstream data context in the workflow. See Passing Data Between Actions for how to set it and reference the result from downstream nodes.Here we demonstrate how to refer to this data using the prefix $result_object_key.