Submit Human Input Form
Submit the recipient’s response to a paused Human Input form. The workflow resumes on acceptance; follow subsequent events via the Stream Workflow Events endpoint. Requires WebApp delivery.
Authorizations
API Key authentication. For all API requests, include your API Key in the Authorization HTTP Header, prefixed with Bearer . Example: Authorization: Bearer {API_KEY}. Strongly recommend storing your API Key on the server-side, not shared or stored on the client-side, to avoid possible API-Key leakage that can lead to serious consequences.
Path Parameters
Access token for the paused form, returned in the human_input_required event from the Run Workflow or Send Chat Message endpoint in streaming mode.
Body
Submitted values keyed by each input's output_variable_name. Paragraph and select inputs take a string; a file input takes one file mapping; a file-list input takes an array of file mappings. A file mapping is {transfer_method: local_file, upload_file_id, type} or {transfer_method: remote_url, url, type}, where type is one of the field's allowed_file_types (image, document, audio, video, custom). For local_file, upload_file_id is the id from Upload File. Use a consistent user across the run, upload, and submit.
ID of the action button the recipient selected. Must match one of the id values from the form's user_actions list (returned by Get Human Input Form).
Identifier for the end user, defined by your application's rules and unique within the app. Service API and WebApp user IDs are separate, even when identical.
Response
Form submitted successfully. The response body is an empty object.
The response is of type object.