Connecting Twitch & YouTube
Zappify talks directly to the official Twitch (EventSub) and YouTube (Data API v3) APIs. Without a connection the event modules receive no data. Streamer.Bot is no longer required. Incoming Twitch raids have been arriving straight from Twitch since 1.0.13 (raid sound, raid bubble, automation, Chaos Counter and statistics react on their own). There is also the official Twitch shoutout: automatically on a raid (Other settings → Raid & shoutout, off by default, with a minimum number of raid viewers, a delay and your own chat message), via the chat command !so <channel> (alias !shoutout, default: moderator and up) or as an automation action. Since 1.0.14 Zappify also detects stream start and stream end on YouTube – so resetting the goal bar, a new Scare Meter session, the automatic end screen, start/end sounds and rules with "Stream start"/"Stream end" work there too. Starting Zappify in the middle of a running stream does not count as a stream start. Since 1.0.21 Zappify tracks the daily YouTube quota (reset at midnight Pacific time). From 80 % you get a notice and likes are queried less often, from 95 % likes, subscriber count and profile pictures pause – chat keeps running. If the quota is used up, Zappify tells you until when YouTube chat is paused and reconnects by itself afterwards. New in 1.0.22: if Twitch or Google rejects the saved login (revoked in the account settings, password changed, expired), Zappify shows "Reconnect needed" in the connection indicator and under Settings → Connections, plus a notice once per session that jumps there. If an access token expires early, Zappify fetches a new one automatically and retries the action. Every request to Twitch, YouTube, Ko-fi and Discord now has a time limit – after a short Wi-Fi drop or standby nothing stays stuck until a restart. Since 1.0.24: if Twitch sends an event twice on a reconnect, Zappify shows it once and books points once. “First message in stream” also works when Zappify stays open across several streams. Since 1.0.25: The Twitch login is checked every hour – if it was revoked, Zappify reports it right away (notice in the Control Panel and in the Quick Control bell). If no YouTube stream is live yet, Zappify waits without an error, checks for the stream start every minute (1 quota unit per check) and then connects the live chat automatically; the startup check shows “Waiting for stream start”. The new raid planner needs two additional Twitch permissions (read followed channels, start raids) – reconnect Twitch once.
Trigger One-time, in the control panel under Settings → Platforms.
Requirements
- A Twitch and/or YouTube account you stream with.
- For YouTube: a livestream that is actually live at the moment you connect.
- No client secret, no app registration — the app ships its own credentials (PKCE).
- Developer note: scopes https://www.googleapis.com/auth/youtube.readonly required for YouTube API.
Step by step
- Open the control panel, go to Settings → Platforms.
- Click "Connect with Twitch". Your system browser opens the consent screen — confirm it.
- After confirmation Twitch redirects back to 127.0.0.1:4290 (Twitch) or 4291 (YouTube). As long as the app is used, refresh tokens remain valid and auto-refresh in the background.
- For YouTube, go live on YouTube first, then click "Connect with YouTube" in the app and confirm the Google consent.
- Done — the status shows "connected" and the event modules now receive data.
If it doesn't work
- "No active YouTube livestream found": the liveChatId only exists during a running broadcast. Go live first, then connect.
- "OAuth state mismatch": the browser redirect arrived too late or from a different window. Start the connect again.
- "quotaExceeded" on YouTube: the shared daily quota is used up. Either wait until 00:00 PT or create your own Google Cloud project (enable YouTube Data API v3, OAuth client as a web application with redirect http://127.0.0.1:4291/oauth/youtube/callback) and enter the client ID/secret in the platform settings.
- Twitch can be connected any time, even offline — only YouTube needs the live stream.
- Firewall: Make sure local ports 4290 and 4291 are not blocked by a third-party firewall.
- Channel point redemptions do not arrive: the permission for them is new since version 1.0.12 — disconnect and reconnect Twitch once. Channel points are only available for affiliate and partner channels; stream start and stream end are detected without reconnecting.
- Shoutouts do not work: Twitch needs an additional permission for them (new in 1.0.13) – disconnect and reconnect Twitch once. Incoming raids work without reconnecting. The "Ready to go?" check on the home tab shows which permissions are missing.
- Stream start is reported twice, by Twitch and YouTube: if you stream to both platforms at once you get the event from both. Filter with the "Platform" condition in automation rules.
- YouTube chat paused because of quota: with the shared Zappify client ID you share the quota with others. Your own client ID under Settings → “YouTube API credentials” gives you your own quota; the Ready check leads you straight there.
- "Reconnect needed": the login was revoked at Twitch or Google, or it has expired. Reconnect the platform under Settings → Connections; the notice disappears on its own afterwards.
- The startup check lists “Raid planner” as missing: the new Twitch permissions are not granted yet. Disconnect and reconnect Twitch under Settings → Connections.
Last updated: 12 November 2026