Overview
This node acts as a trigger for Twitch events by subscribing to Twitch EventSub webhooks. It listens for specific Twitch channel-related events such as when a stream goes online or offline, when a channel is followed, raided, or updated. When the specified event occurs on the chosen Twitch channel, the node activates and outputs the event data.
Common scenarios where this node is useful include:
- Automatically notifying a community or team when a Twitch streamer goes live.
- Tracking follower activity or raids on a channel for analytics or alerts.
- Triggering workflows based on channel updates like title or category changes.
For example, you could use this node to start a workflow that posts a message to a Discord server whenever your Twitch stream goes online.
Properties
| Name | Meaning |
|---|---|
| Event | The Twitch event type to listen for. Options: Channel Follow, Channel Raid, Channel Update, Stream Offline, Stream Online. |
| Channel | The Twitch channel name (login) to monitor for the selected event. |
Output
The node outputs JSON data representing the payload received from Twitch's webhook for the subscribed event. This JSON contains detailed information about the event, such as user IDs, timestamps, and other event-specific data provided by Twitch.
If the incoming webhook request includes a challenge (used during webhook subscription verification), the node responds with the challenge string but does not output workflow data in that case.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for Twitch API authentication.
- Needs proper configuration of Twitch API credentials with client ID and client secret.
- The node uses Twitch EventSub webhooks, so the environment must allow receiving HTTP POST requests at the configured webhook URL.
- The node internally calls Twitch API endpoints to manage webhook subscriptions and verify credentials.
Troubleshooting
- Webhook subscription failures: If the node cannot create or find an existing webhook subscription, ensure the Twitch credentials are valid and have the necessary permissions.
- Authentication errors: Errors obtaining the access token usually indicate invalid client ID or secret. Verify these credentials.
- Webhook callback unreachable: Twitch requires a publicly accessible HTTPS endpoint. Make sure the webhook URL is reachable from the internet.
- Event data missing or empty: Confirm the correct channel name and event type are set; also check that the Twitch channel has relevant activity.
- Error messages related to access tokens: These typically mean the OAuth token request failed. Check network connectivity and credential correctness.