For the complete documentation index, see llms.txt. This page is also available as Markdown.

Twitch

Use the Twitch library to read stream, channel, user and game information, and to create a clip when the selected account has the required permission. Select a stored Twitch connection in Vault; keep its authentication values out of flow descriptions, prompts and screenshots.

Find the installed library

In an MSP workspace, open MSP Hub → Catalog → App Store → Installed and locate Twitch. Open the library details to inspect the actions available in that environment.

The screens checked on 14 October 2026 listed 13 actions. The Installed tile displayed version 1.0.3 and the detail screen displayed Current Version 1.0.4. These are labels from the checked environment; confirm your installed package before comparing action fields.

Inspect the 13 Twitch actions in the checked library details. The Current Version label in this screen is specific to this environment.
Inspect the 13 Twitch actions in the checked library details. The Current Version label in this screen is specific to this environment.

Available actions

The following inputs come from the installed action catalogue checked on 14 October 2026. Availability depends on the installed library and your licence. Authentication and provider permissions are separate requirements.

Action
Declared action inputs

Create Clip

Broadcaster ID (broadcaster_id), required string. Creates external content; use an approved test stream.

Get Banned Users

Number Size per Page (first), required string, default 20; catalogue describes a range of 1–100.

Get Channel Emotes

No additional action inputs declared.

Get Channel Information

No additional action inputs declared.

Get Channel Teams

No additional action inputs declared.

Get Chatters

Number Size per Page (first), required string, default 100; catalogue describes 1–1,000. Moderator ID (moderator_id), required string; the catalogue requires it to match the token's user ID.

Get Clips

ID (selection), Number Size per Page (first, default 20) and ID Type (type); all required strings. Choose the ID type offered by the installed action before supplying its matching ID.

Get Game

ID Type (type) and ID (selection), required strings.

Get Global Emotes

No additional action inputs declared.

Get Stream Tags

No additional action inputs declared.

Get Teams

ID Type (type), required string.

Get Top Games

Number Size per Page (first), required string, default 20; catalogue describes a range of 1–100.

Get User

No additional action inputs declared.

“No additional action inputs declared” does not mean that a connection or provider authorization is unnecessary. Check the installed action form and connection context. The catalogue read did not expose selector choices or a returned-output schema.

Configure a first read-only example

  1. Create an isolated development Hyperflow and add Twitch → Get Top Games.

  2. Select an approved Twitch connection from Vault.

  3. Set Number Size per Page to 20.

  4. Save the development version. When an authorized provider test is available, run it once.

  5. Inspect the action status and returned data in the operation log. Record the actual shape of the response before binding fields into a later action.

This example uses the catalogue’s configuration contract. A live Twitch request and its response were not tested for this guide. Confirm the connection with an authorized test before relying on its data.

Discover the action contract through MCP

Ask your connected assistant: “List the installed Twitch actions and show the required inputs for Get Top Games. Do not run or change anything.”

The assistant can browse the library, retrieve the action reference from the action search, and read its declared inputs. These are catalogue reads; they do not call Twitch or start a Hyperflow. Use the action reference returned by the current search rather than constructing one from an action label.

See the Vault guide for stored connections.

Use Read run history and failure evidence to interpret the matching run and its logs.

Use Cases

FAQ

Was this helpful?