Forms & SurveysReal-timeUpdated May 2026

Twitch

Twitch stream data and user info

Twitch is the live-streaming platform for gaming and creator content — Tiny Command exposes basic read actions for Twitch's Helix API. Two actions, no triggers (Twitch event subscriptions go via the EventSub system; for "react to stream-started" workflows, configure EventSub to a Tiny Command webhook trigger URL): Get Stream Info (current live stream data for a user — title, game, viewer count, started_at, language; returns empty if offline), Get User (user profile by login or ID). The connection uses Twitch OAuth (or App Access Token for app-level operations). For workflows that monitor specific streamers or react to "this streamer just went live" events, EventSub subscriptions are the right path; this connector covers the read side. Useful for "auto-post to Discord when our team streamer goes live" personal-automation patterns.

Connect Twitch

0triggers

2actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything Twitch can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Get Stream Info	Fetches the current live stream details for a Twitch user (title, game, viewer count, started_at). Returns empty if the channel is offline.	1 fields	View →
Get User	Fetches a Twitch user's profile (login, display name, broadcaster type, description, view count) by user ID or login.	1 fields	View →

Recipes

Pre-built Twitch workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Twitch → Slack alerts

AI-triage every Twitch event, ping the right channel only when it matters.

Twitch → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

Twitch → Notion database

Turn Twitch into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Twitch once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Twitch field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Twitch integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Twitch to Tiny Command?

Open the Tiny Command workflow builder, drop in a Twitch node, and click Connect. Authorize Twitch once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What Twitch triggers does Tiny Command support?

Tiny Command focuses on outbound actions for Twitch today. Use Tiny Command's universal Webhook or Schedule trigger to start Twitch workflows, then run any Twitch action you need.

What Twitch actions can I run from a workflow?

2 Twitch actions are available out of the box, covering forms & surveys operations like "Get Stream Info". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the Twitch integration real-time?

Twitch actions execute synchronously inside your workflow. Tiny Command waits for Twitch's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use Twitch with Tiny Command?

No. Every Twitch trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Twitch API endpoint directly.

How much does the Twitch integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Twitch integration itself has no per-app surcharge.