Changelog

Preferences in workflow run logs

In workflow run logs, you can now see the exact preference set that was evaluated during that workflow run. Previously, this information was not surfaced.

Beyond the new preferences section, you can find some additional changes to this section of the dashboard:

• The overview section of a workflow run log now shows workflow run ID, which is useful for debugging.
• All data about the trigger step is now nested under “trigger” in the workflow run log.
• We added a refetch button if you need to reload a workflow run log. Previously you needed to reload the entire page.
• If your workflow has a delay step, the status is updated in real time, indicating when the step has been completed.

Fixes and improvements

• 👀 We added support for side loading preferences when listing users and objects via the API.
• 👀 We added support for the sum filter in liquid.
• 👀 We added support for filtering subscribers of objects by recipients and for filtering the subscriptions of a recipient by objects.
• 👀 We now show your account name and icon in mobile push previews.
• 👀 We removed variable management from the developers section. It is now only located under settings.

Announcing: send windows

We're excited to announce our newest addition to the Knock workflow engine: send windows.

With send windows, you can tell any channel step in your workflow when it should execute and send a message to your customers. For example, if you want to ensure your customers only receive a given transactional email from your product during working hours, you can set its send window for Monday to Friday, between 9:00 a.m. and 6:00 p.m. local user time.

At Knock our mission is to provide engineering and product teams with tooling that helps them build more thoughtful notification experiences for their users, and send windows is a big step forward towards that vision.

Learn more about send windows in our docs.

Fixes and improvements

• 👀 We added "Reset all uncommitted changes" to email layouts, translations, and event action mappings.
• 👀 We now return an error if the Content-Type header is missing from PUT, POST, PATCH, and DELETE API requests with a body.
• 👀 We moved the account settings page to be a separate page from the rest of the dashboard and refreshed the design.
• 🐛 We fixed an issue where pagination within the subscriptions view in the dashboard may have led to no results being returned when clicking "Next".
• 🐛 We fixed an issue where archived sources were still displaying their events within the event selector on a workflow.

Today we’re releasing SlackKit, a suite of embeddable UIs and APIs that make it simple to connect your product to your customer’s Slack workspace and send notifications to where your customers work.

Behind the scenes, SlackKit:

• manages your OAuth connection and tokens.
• helps your customers select which channels they want to receive notifications in.
• integrates seamlessly with the rest of Knock, so you can easily send notifications to Slack alongside any other channel.

Shipping a Slack integration has never been easier.

Read the full announcement ->

Heap extension for analyzing customer engagement

Today we’re adding support for sending message delivery and engagement data to Heap—a digital insights platform to analyze customer engagement.

This release adds Heap alongside our existing Segment integration as a way to get data out of Knock for analyzing notification usage and engagement.

Note, to correctly analyze custom events in Heap, follow these steps to build new events.

Learn more about our Heap extension in our docs.

Fixes and improvements

• 👀 We improved the way that event payload data shows in the variable pane.
• 👀 We added a new onAuthenticationComplete handler to our SlackAuthButton component in the React SDK.
• 🐛 We fixed an issue with filtering workflows in the workflow run logs view.
• 🐛 We fixed an issue where calling the set tenant API with an invalid payload would return a 500.
• 🐛 We fixed an issue where the workflow template gallery in the dashboard would load in an incorrect initial state.
• 🐛 We fixed an issue where you could pass [null] as valid tokens when setting channel data for push channels.

Introducing our new command menu (cmd+k)

We've added a new way to navigate across the Knock dashboard and perform common actions through our new command menu. The command menu gives you a quick and easy way to:

• Search and navigate to a particular workflow
• Switch between your Knock environments
• Search for a user using their id or email
• Quick copy your API keys
• ... and much more!

You can get started using the command menu in the dashboard by clicking the new "Search" link in the sidebar, or for all those keyboard shortcut lovers, by typing cmd+k.

Fixes and improvements

• 👀 We added a new "Promote" button to the view commit modal to promote the commit to the next environment.
• 🐛 We fixed an issue where using an event type trigger for a workflow would not default the data section in the variable pane.
• 🐛 We fixed a regression in our Node SDK where the remove subscriptions objects method would fail.

New Relic observability extension

Today we’re extending support for reporting notification metrics to New Relic. Previously, we only supported Datadog as an observability platform, but with today’s release, we’re introducing support for reporting metrics to New Relic as well.

You can read more in the documentation about the types of metrics reported. Our New Relic extension is available to customers on our Enterprise plan only.

New outbound webhook event types

Today we're announcing support for new types of events in outbound webhooks, making it even easier to deeply integrate Knock into your application's workflow. With today's release, you can now listen to changes for any version-controlled content within your Knock dashboard, including workflows, email layouts, and translations.

You can find the full set of supported webhook events in the documentation and can create a webhook by going to the "Developers > Webhooks" section in the Knock dashboard.

Fixes and improvements

• 👀 We greatly improved the bundle size in our @knocklabs/react package by removing the dependency on the date-fns library.

Our Flutter SDK

Today we’re shipping our new Flutter SDK, which is a client-side SDK written in Dart to interact with the Knock API and to build in-app notification experiences in Flutter applications.

We have big plans for more in-product experiences that we’ll be bundling into this SDK in the near future. Today’s release is a first step towards that future, giving the base primitives to easily bring all of the functionality of Knock into your applications in an easy-to-consume way.

You can learn more in our Flutter SDK documentation.

Fixes and improvements

• 👀 We added a link to view usage for Enterprise customers under the "Billing" page
• 👀 We redesigned the empty states across the dashboard
• 🐛 We fixed an issue where our Vonage integration would fail when sending multi-part messages

Announcing commit diffs

Today we’re releasing a big upgrade to the version control experience in Knock with commit diffs.

With this release, you can now:

• View a commit to see what has changed between that commit and the prior version of the workflow.
• Review a diff when promoting a commit to an environment. You will see the diff between the current state of that environment and the pending commit.
• Audit the full history of commit diffs in your commit log to know exactly what's changed over time.

Read the full announcement here —>

New Android SDK

Today, we’re shipping our new Android SDK, which is a client-side SDK written in Kotlin to interact with the Knock API and to build in-app notification experiences in Android applications.

We have big plans for more in-product experiences that we’ll be bundling into this SDK in the near future. Today’s release is a first step towards that future, giving the base primitives to easily bring all of the functionality of Knock into your applications in an easy-to-consume way.

You can learn more in our Android SDK Documentation, or get started now by following the installation instructions.

Fixes and improvements

• 👀 We added support for edge runtimes, like Vercel and Cloudflare Workers, in our Node JS SDK
• 👀 We now show a channel data tab when viewing an individual tenant in the dashboard

New React SDK

Today, we’re shipping our new React SDK (@knocklabs/react), which provides a unified set of hooks and components for integrating Knock into your web applications. You can use our React package to power in-app notification experiences like feeds, toasts, and banners for your users, as well as powering notification configuration via our preferences API.

Our new SDK is the home of all in-product notification experiences powered by Knock, superseding the previous react-notification-feed package. If you’re using the old package, you can read here on how to migrate.

We have big plans for more in-product experiences that we’ll be bundling into this package in the near future. Today’s release is a first step towards that future, giving the base primitives to easily bring all of the functionality of Knock into your applications in an easy-to-consume way.

You can install the React SDK from NPM by running npm install @knocklabs/react and can find the package in our brand new Javascript monorepo.

Fixes and improvements

• 👀 We improved the loading time of message views within the Dashboard
• 👀 We now validate certificates when configuring an APNS channel
• 👀 We now validate the service account JSON when configuring a FCM channel