Short answer: Drop the "HeyGen → List HeyGen Avatars" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
{}
{"data": {"avatars": [{"gender": "female","avatar_id": "a_abc","avatar_name": "Daisy","preview_image_url": "https://x.com/i.jpg"}]},"error": null}
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.