Overview
This node listens for specific Twitch events using webhooks and triggers workflows when those events occur. It is useful for automating responses to Twitch channel activities such as when a stream goes online or offline, when a channel is followed, raided, or updated.
Common scenarios include:
- Notifying a Discord channel when a Twitch stream goes live.
- Logging follower events for analytics.
- Triggering alerts or actions when a raid happens on a channel.
- Updating external systems when channel information changes.
Properties
| Name | Meaning |
|---|---|
| Event | The Twitch event 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 webhook payload received from Twitch for the subscribed event. This data contains detailed information about the event, such as user IDs, timestamps, and event-specific details.
If the incoming request is a webhook verification challenge from Twitch, the node responds accordingly but does not output workflow data.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token credential for Twitch API access.
- Needs internet access to receive webhook callbacks from Twitch.
- The node uses Twitch's EventSub system, so the Twitch account must have appropriate permissions to create webhook subscriptions.
- The node internally calls Twitch API endpoints to manage webhook subscriptions and retrieve user information.
Troubleshooting
- Channel not found error: Occurs if the specified channel name does not exist or cannot be resolved via the Twitch API. Verify the channel name is correct.
- Webhook subscription failures: Can happen if the Twitch API credentials are invalid or lack required scopes. Ensure the API key has proper permissions.
- Webhook callback URL issues: Twitch requires a publicly accessible HTTPS URL for webhook callbacks. Make sure the n8n webhook URL is reachable from the internet.
- Event data missing or empty: Confirm that the Twitch event type matches the expected event and that the channel is active or relevant for that event.
- If the node logs show errors during subscription creation or deletion, check network connectivity and Twitch API status.