{ "$result_object_key": { "appointment_id": "Identifier of the associated appointment", "client_email": "Email address of the client", "client_id": "Unique identifier for the client", "client_name": "Name of the client", "id": "Unique identifier for the note", "last_modified_at": "Timestamp when the note was last modified", "note_name": "Name of the note", "practitioner_email": "Email of the practitioner", "practitioner_id": "Unique identifier for the practitioner", "practitioner_name": "Name of the practitioner", "questions": { "answer": "Answer to the question", "attachments": { "content_type": "Content type of the attachment", "file_name": "Name of the attached file", "id": "Unique identifier for the attachment", "url": "URL of the attachment" }, "client_profile_field_id": "ID of the client profile field this question maps to", "column_names": "Column names for table/grid questions", "id": "Unique identifier for the question", "office_note": "Office note for the question", "office_use": "Whether the question is for office use only", "question_type": "Type of the question", "rows": { "answers": "Answers for each column in the row", "text": "Text for the row" }, "text": "Text of the question" }, "status": "Status of the note", "timestamp": "Timestamp when the note was created (called `Date` in the IntakeQ API)" }}
{ "$result_object_key": { "appointment_id": "Identifier of the associated appointment", "client_email": "Email address of the client", "client_id": "Unique identifier for the client", "client_name": "Name of the client", "id": "Unique identifier for the note", "last_modified_at": "Timestamp when the note was last modified", "note_name": "Name of the note", "practitioner_email": "Email of the practitioner", "practitioner_id": "Unique identifier for the practitioner", "practitioner_name": "Name of the practitioner", "questions": { "answer": "Answer to the question", "attachments": { "content_type": "Content type of the attachment", "file_name": "Name of the attached file", "id": "Unique identifier for the attachment", "url": "URL of the attachment" }, "client_profile_field_id": "ID of the client profile field this question maps to", "column_names": "Column names for table/grid questions", "id": "Unique identifier for the question", "office_note": "Office note for the question", "office_use": "Whether the question is for office use only", "question_type": "Type of the question", "rows": { "answers": "Answers for each column in the row", "text": "Text for the row" }, "text": "Text of the question" }, "status": "Status of the note", "timestamp": "Timestamp when the note was created (called `Date` in the IntakeQ API)" }}
{ "$result_object_key": { "appointment_id": "Identifier of the associated appointment", "client_email": "Email address of the client", "client_id": "Unique identifier for the client", "client_name": "Name of the client", "id": "Unique identifier for the note", "last_modified_at": "Timestamp when the note was last modified", "note_name": "Name of the note", "practitioner_email": "Email of the practitioner", "practitioner_id": "Unique identifier for the practitioner", "practitioner_name": "Name of the practitioner", "questions": { "answer": "Answer to the question", "attachments": { "content_type": "Content type of the attachment", "file_name": "Name of the attached file", "id": "Unique identifier for the attachment", "url": "URL of the attachment" }, "client_profile_field_id": "ID of the client profile field this question maps to", "column_names": "Column names for table/grid questions", "id": "Unique identifier for the question", "office_note": "Office note for the question", "office_use": "Whether the question is for office use only", "question_type": "Type of the question", "rows": { "answers": "Answers for each column in the row", "text": "Text for the row" }, "text": "Text of the question" }, "status": "Status of the note", "timestamp": "Timestamp when the note was created (called `Date` in the IntakeQ API)" }}
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.