Notify Discourse users about your livestream with Twitch EventSub and Courier
Aydrian Howard
January 13, 2021
On January 6, Riley Napier joined me for our first Courier Live of the new year. Having recently set up webhooks using Twitch EventSub, I wanted to walk through how you could trigger notifications about your Twitch livestreams using Courier. We did this using a Glitch application and explained how to set it up and start accepting requests from Twitch. We then created a notification in Courier and used the Webhook Provider to make a request to the Discourse API to display a banner on the community forum.
Check out the video below to watch us:
- Walk through receiving a Twitch EventSub event using a Glitch application.
- Use the Courier Webhook Provider to use the Discourse API to display a banner on the forum.
- Use Jsonnet to personalize the Discourse banner content.
Code for the Node.js/ExpressJS server to handle the Twitch EventSub requests can be found in the Courier Twitch EventSub Glitch application. Remix it and start sending your own Twitch notifications.
Be sure to Like the video and Subscribe to our YouTube channel.
Is there something you’d like to see us do using Courier? Let us know and it might be the subject of our next Courier Live. Follow us on Twitch to be notified when we go live.
-Aydrian
Similar resources
Vibe Coding Notifications: How to Use Courier with Cursor or Claude Code
Courier's MCP server lets AI coding tools like Cursor and Claude Code interact directly with your notification infrastructure. Unlike Knock and Novu's MCP servers that focus on API operations, Courier's includes embedded installation guides for Node, Python, Flutter, React, and other platforms. When you prompt "add Courier to my app," your AI assistant pulls accurate setup instructions rather than relying on outdated training data. OneSignal's MCP is community-maintained, not official. Courier supports 50+ providers, native Slack/Teams integration, drop-in inbox and preference components, and a free tier of 10,000 notifications/month. Configure in Cursor with "url": "https://mcp.courier.com" and "headers": { "api_key": "YOUR_KEY" }.
By Kyle Seyler
January 22, 2026
The Complete Guide to B2B Customer Engagement
Courier provides the notification infrastructure layer for B2B customer engagement, routing messages across email, SMS, push, in-app, Slack, and Teams based on user preferences and product events. Unlike building notification systems in-house—which takes months of engineering time for features like multi-channel routing, preference management, and delivery tracking—Courier handles this infrastructure so product teams can focus on engagement strategy. B2B customer engagement requires multiple layers: notification infrastructure (Courier), customer data platforms (Segment), product analytics (Mixpanel/Amplitude), and channel-specific tools. Companies with strong engagement programs see 15-25% churn reduction. The key is connecting product events to customer communication at the right moment through the right channel, handling complexity like multiple users per account with different notification needs across work channels.
By Kyle Seyler
January 20, 2026
Customer Engagement Platform vs CRM: Key Differences Explained
A CRM stores customer data: contacts, purchases, support tickets, and pipeline. It answers "who are our customers?" A customer engagement platform (CEP) orchestrates communication across email, push, SMS, in-app, and chat. It answers "what should we tell them next?" CRMs focus on historical records. CEPs process real-time behavior and trigger messages based on actions. Most teams need both, plus a third layer: notification infrastructure for reliable multi-channel delivery. Courier bridges CEP and infrastructure by combining routing, failover, and delivery tracking with engagement features like preference management, visual templates, and in-app notification centers.
By Kyle Seyler
January 07, 2026
© 2026 Courier. All rights reserved.