For software products of every scale, emails are the de facto standard for notifying your users. It’s a fast, cost-effective, and readily accessible channel for reaching your users, especially if you’re sending transactional emails or generating event-driven alerts. In this post, I’ll go over three ways to send emails with Python. Apps can leverage Python for sending emails for an array of use cases.
Need help getting started with an integration? Or curious what we’ve launched lately? With our in-app support center, you have everything you need to build and send notifications in one convenient spot. Check out our new support center here. To see the latest feature releases, what’s in development right now, and what’s on our future roadmap – including updates that don’t make our monthly highlights – visit updates.courier.com.
Almost every web application needs the functionality to send transactional emails in response to various triggers. Events like account registration, password resets, purchase receipts, and user verification are among the many tasks today’s applications need to accomplish via email. These emails are crucial for notifying users of important updates and enabling key user workflows in your application. This post explores three different options for sending email from within a Node.js app.
On February 2nd and 3rd, Shy Ruparel joined me for another Courier and Contentful crossover stream. This time, we decided to play around with an IoT E-ink display and use it to show the latest posts from Contentful and send notifications using Courier. During Tuesday's Contentful Live we started working with the newly released Adafruit MagTag. The MagTag is a 2.9" grayscale E-Ink display that can show data on its screen even when power is removed.
If your application sends emails to confirm new accounts, reset user passwords, or handle billing and invoicing, then it’s sending transactional emails. This kind of functionality is extremely common, so naturally there are a lot of vendors that provide these services. But which transactional email API is right for your application?
In this series, I explain how to use Twitch EventSub and Courier to automatically send notifications to multiple destinations – Slack, Discord, and more – when your Twitch stream goes live. In part one, we built a Node.js app using Express.js to accept events from Twitch EventSub. In part two, we listened for our event and triggered a notification using Courier. Now, in part three, we're going to use Courier’s List API to send multiple notifications when our event is triggered.
A push notification. A bolded channel. A red badge next to an unread conversation. These are all ways that Slack manages your attention. For the messaging giant, managing attention is deeply intertwined with their mission of making work life more productive. Too much noise and suddenly what was an invaluable collaboration hub turns into a distraction. Not enough and it’s just another tool gathering virtual dust.
In this series, I explain how to use Twitch EventSub and Courier to automatically send notifications to multiple destinations – Slack, Discord, and more – when your Twitch stream goes live. In part one, we built a Node.js app using Express.js to accept events from Twitch EventSub. Now, in part two, we’re going to listen for our event and trigger a notification using Courier.
Today, we’re excited to announce the release of Environments in Courier. You can now create, preview, and troubleshoot your notifications in a test environment before going live. With support for two environments – Test and Production – you no longer have to worry about accidentally sending a notification to your users before you’re ready.
