Short answer: Drop the "Hume AI → List Hume Octave Voices" 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 |
|---|---|---|---|
Provider provider | options | Optional | Provider. Options: Hume, Custom (mine) |
{"provider": "{{trigger.provider}}"}
{"voices": [{"id": "v_abc","name": "Male English Actor","description": "Warm, charismatic, clear"}]}
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.