Short answer: Drop the "Twitch → Get User" 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 |
|---|---|---|---|
Username login | string | Required | Username. Example: ninja |
{"login": "e.g. ninja"}
{"data": [{"id": "123456","login": "ninja","created_at": "2011-11-20T00:00:00Z","view_count": 500000000,"display_name": "Ninja","broadcaster_type": "partner","profile_image_url": "https://..."}]}
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.