{ "$result_object_key": { "category": { "id": "Unique identifier for the charge category", "name": "Name of the charge category" }, "charge_item": { "code": "Code identifying the charge item", "code_type": "Type of code (e.g., CPT, ICD)", "id": "Unique identifier for the charge item", "name": "Name of the charge item", "price_in_cents": "Default price of the charge item in cents" }, "created_at": "Timestamp when the charge was created", "description": "Description of the charge", "id": "Unique identifier for the charge", "invoice": { "id": "Unique identifier for the invoice", "invoice_number": "Invoice number", "status": "Status of the invoice", "url": "URL to view the invoice" }, "name": "Name of the charge", "price_in_cents": "Price of the charge in cents", "quantity": "Quantity of the charge", "service_date": "Date when the service was provided", "status": "Status of the charge", "updated_at": "Timestamp when the charge was last updated" }}
v1
Create Charge
Documentation for the Create Charge action for Hint Health
{ "$result_object_key": { "category": { "id": "Unique identifier for the charge category", "name": "Name of the charge category" }, "charge_item": { "code": "Code identifying the charge item", "code_type": "Type of code (e.g., CPT, ICD)", "id": "Unique identifier for the charge item", "name": "Name of the charge item", "price_in_cents": "Default price of the charge item in cents" }, "created_at": "Timestamp when the charge was created", "description": "Description of the charge", "id": "Unique identifier for the charge", "invoice": { "id": "Unique identifier for the invoice", "invoice_number": "Invoice number", "status": "Status of the invoice", "url": "URL to view the invoice" }, "name": "Name of the charge", "price_in_cents": "Price of the charge in cents", "quantity": "Quantity of the charge", "service_date": "Date when the service was provided", "status": "Status of the charge", "updated_at": "Timestamp when the charge was last updated" }}
{ "$result_object_key": { "category": { "id": "Unique identifier for the charge category", "name": "Name of the charge category" }, "charge_item": { "code": "Code identifying the charge item", "code_type": "Type of code (e.g., CPT, ICD)", "id": "Unique identifier for the charge item", "name": "Name of the charge item", "price_in_cents": "Default price of the charge item in cents" }, "created_at": "Timestamp when the charge was created", "description": "Description of the charge", "id": "Unique identifier for the charge", "invoice": { "id": "Unique identifier for the invoice", "invoice_number": "Invoice number", "status": "Status of the invoice", "url": "URL to view the invoice" }, "name": "Name of the charge", "price_in_cents": "Price of the charge in cents", "quantity": "Quantity of the charge", "service_date": "Date when the service was provided", "status": "Status of the charge", "updated_at": "Timestamp when the charge was last 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.