Short answer: Drop the "Hume AI → Hume Expression Measurement" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
URLs urls | array | Required | Audio/video/text URLs to analyze |
Face Model models_face | options | Optional | Face Model. Options: No, Yes |
Voice/Prosody Model models_prosody | options | Optional | Voice/Prosody Model. Options: Yes, No |
Language Model models_language | options | Optional | Language Model. Options: No, Yes |
{"urls": "{{trigger.urls}}","models_face": "{{trigger.models_face}}","models_prosody": "{{trigger.models_prosody}}","models_language": "{{trigger.models_language}}"}
{"job_id": "job_abc"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.