News for hackers. Stuff that matters.
Re:Launch HN: Courier (YC S19) – Developer infrastructure fo... by tejaskumthekar on Wednesday March 02, 2022 @11:56AM (#30529515)
Gotcha! I think easiest way would be a. You'd configure Mailchimp details (api key etc) inside Courier's provider/integrations interface b. Invoke Courier API and Courier would route it to Mailchimp

["a" can be any integration Courier supports - so it could be Twilio for SMS for instance] ["b" changes based on how you invoke the API - so you could do send just an email via Mailchimp, send just an SMS via Twilio OR both email and SMS OR SMS if email fails and so on --- this logic is configurable via both UI and API]

Re:Launch HN: Courier (YC S19) – Developer infrastructure fo... by freeqaz on Wednesday March 02, 2022 @12:04PM (#30529643)
Ahhh, okay thank you for clarifying. The "stacked notifications", especially if something fails, makes total sense. That is what made it "click" in my head where Courier fits in the stack.

I remember Troy explaining this when we spoke about picking the best "channel" to actually reach somebody, but I guess I forgot.