The last couple months have been quiet ones here on the Knock changelog. That's because we were heads down on our first ever launch week. Here's a recap of each of the 5 big changes we shipped.
HTTP Source
HTTP Source lets you trigger your multi-channel notifications from any source that can stream events into Knock. This includes dedicated streaming infrastructure, such as Kafka and Kinesis, as well as any product that can stream events and webhooks (think Supabase functions and Radar location-based events.)
This means you can power Knock with even more parts of your infrastructure to send notifications that are relevant for your customers.
CLI and management API
Now developers can work with Knock resources in code, and automate pushing that code back into Knock to run on our platform. Read our docs to learn how you can scale notifications on Knock while managing our system from your CI/CD environment.
The Knock CLI and management API release is a big step forward for both Knock’s developer experience and for what you can build on top of our platform.
Schedules API
Schedules API is a declarative, code-first way to build recurring notification schedules and to give your users the ability to control when they receive those notifications. We also introduce timezone aware sending with this release, making it even easier to send the right notification at the right time with Knock.
Webhook channel
Webhook channels bring a new level of flexibility and extensibility to Knock’s output layer. You can use webhook channels to notify internal service within your application, or 3rd-party apps such as PagerDuty or Zapier.
The best part of webhook channels is they tie into Knock’s preferences model, so you can surface them to your customers.
Subscriptions API
With subscriptions, you can model lists of users, then notify all users in that list with a single API call.
Subscriptions are a powerful way for you to offload to Knock the responsibility of who should be notified. You can use subscriptions to power alerting use cases and publish/subscribe models, or to model the concept of a set of dynamic followers of a resource.