Changelog

Today we're introducing new device-level metadata for tracking per-device locale and timezones for push channel data. Previously, push channel data was limited to tracking only tokens. Now, with device-level metadata, you can attach an additional timezone and locale field along with your token, and Knock will automatically evaluate them when sending push notifications.

Here's how it works:

• Using the per-device locale you can localize push notification content to what your user's device has configured, taking precedence from the locale stored on the user. That means if your device is set to en-GB but your user has en-US on their user properties, any push notifications sent to the device will be generated in British english.
• Similarly, using the per-device timezone you can control the precise send windows for when a particular device for a user should receive a push notification. This per-device value takes precedence over the user property.

Our client-side mobile SDKs have been updated with the ability automatically set this data for each device, or if you're using our API directly, you can replace the call to set tokens with a list of devices.

{
  "devices": [
    {
      "token": "user_device_token_1",
      "locale": "en-US",
      "timezone": "America/New_York"
    }
  ]
}

Push device metadata is available today for all customers. You can read more in our documentation.

Fixes and improvements

• 👀 [Dashboard/mAPI/CLI] You can now opt into a private beta of branching. Head to your "Settings > Branches" page to request access.
• 👀 [Dashboard] We added the ability to see all subscriptions that a user has from the users detail page.
• 🐛 [Notification engine] We fixed an issue with our workflow trigger function where some child workflows were not running.
• 👀 [API] We now expose a channel attached to each message produced from the API and sent via webhooks.
• 👀 [mAPI] You can now filter commits by one or more resource_type (like workflow) to show all commits associated to that type of resource.
• 👀 [Notification engine] We added a new compare_versions liquid filter.
• 👀 [Notification engine] We now send workflow_category as a tag to Datadog and NewRelic when reporting metrics.
• 👀 [Dashboard] You can now see the "Last login at" for the members of your account.

Today we're introducing a new preference primitive: channel-level preferences.

While we've always had channel type preferences that let you control preferences for all messages sent for that channel type (like email), there were situations where you might have needed to be more granular with exactly what a user is opting out of.

As an example, if you're using our webhook channel to send messages in your workflow to both "PagerDuty" and "Incident.io", you would have no way in our existing preference model to set a preference for each of these channels, as both would be represented under the http channel type.

Now, using per-channel preferences, you can control exactly which channel a user should or should not receive messages from.

{
  "channels": {
    // The PagerDuty channel
    "145a7412-2e9a-4ae4-ae2d-cbca4f5308fe": true,
    // The Incident.io channel
    "8b3c9f21-7d4a-4e1b-9c8e-f2a1b5d6c3e9": false
  }
}

Channel-level preferences work just like channel type preferences in that you can nest them under workflows or categories. They can even be mixed with channel_types.

{
  "workflows": {
    "new-incident": {
      "channels": {
        // PagerDuty channel is OFF
        "145a7412-2e9a-4ae4-ae2d-cbca4f5308fe": false
      },
      "channel_types": {
        // All emails
        "email": true
      }
    }
  }
}

Channel-level preferences are available today for all customers. You can read more in our documentation.

Fixes and improvements

• 👀 [CLI] All resources pulled by the CLI now have $schema fields attached, making it possible to get an editing assist when working with your schemas locally.
• 👀 [mAPI] We've introduced new per-channel step level schemas in our OpenAPI spec to aid with editing. Instead of WorkflowChannelStep there's now WorkflowEmailStep, WorkflowInAppFeedStep etc.
• 👀 [Dashboard] We've made some large performance improvements to the template editor within the dashboard. Previously, large documents with frequent saves were causing the performance of the editor to regress. Now things should be silky smooth!
• 🐛 [Dashboard] We fixed an issue with the toolbar commands in our template editor.
• 🐛 [Dashboard] We fixed an issue where autocompleting objects in liquid would show an empty value.
• 🐛 [Notification engine] We fixed an issue where using a null actor on the workflow trigger step could cause it to fail.

Today we're excited to release Knock Guides 1.0.

With Guides, you use your own components to power in-app messages that drive activation and upsells. Legacy in-app messaging vendors use external JavaScript libraries that bloat performance and degrade your design. Our component-first infrastructure keeps your app fast and your messaging on-brand.

Component-first in-app messaging

Guides are managed from the Knock dashboard. Once you hook a component into Knock, it's available for product managers and marketers to draft and preview content for that component, as well as target the audience for the guide and where it should render in your application.

Guide prioritization and throttling

You can manage guide prioritization and throttling to ensure users see the highest priority guides first and aren't flooded with messages when they log in to your product.

Observability and analytics

Knock Guides use the same powerful observability and analytics engine as the rest of Knock. Every guide records per-user events so you understand when users see, interact with, and archive your guides.

All of that data is available for debugging and analysis within the Knock dashboard, and will automatically flow through any extensions you've set up with Knock, like our data warehouse syncs or message event webhooks.

Key benefits

• Composable primitives to build what you want. The guides toolkit provides React components, React hooks, lower-level JavaScript APIs, socket infrastructure so your engineers can build the in-product experience they want.
• No performance tax. No external scripts to load, no performance tax. Your in-app messaging code runs through the same build process as the rest of your app.
• Actual inline components. Complete control over your render lifecycle so you can ship truly embedded messaging without content layout shift, UI jank, or CSS conflicts.

Get started

Guides are available for all Knock customers starting today. You can get started by reading our documentation.

Today we're introducing reusable requests, making it easy to reuse fetch step configurations across different workflows.

Save reusable requests

In the dashboard sidebar, you'll see a new "Reusable requests" section. Here you can create and manage your reusable requests that can be used in any fetch step across your workflows.

Once saved, these requests can then be applied to any workflow fetch step, making it easy to maintain consistent configurations across your messaging infrastructure.

Apply reusable requests to workflow fetch steps

Within a workflow fetch step, you'll see a new "Apply template" button. Here you can select a reusable fetch step to instantly inherit its properties. While linked, the fetch step will continue to inherit any changes made to the reusable request's configuration.

AI-generate reusable request configurations

We've also added the ability to generate reusable request configurations. This can be done by clicking the "Generate" button in the reusable request editor either during creation or when editing an existing request. This will use the prompt to auto-populate the request configuration.

More Information

To learn more about reusable requests, check out the documentation: Reusable fetch functions.

Fixes and improvements

• 👀 [Dashboard] Added realtime input validation in the content editor
• 👀 [Liquid] Added support for partial ISO dates across all of our date helpers
• 👀 [Dashboard] Added message previews to the Guide message log
• 👀 [Dashboard] Fixed performance issues in Guide content editor
• 👀 [SDKs] Added optimistic updates when archiving a message
• 🐛 [API] Fixed a bug with creating schedules with a null ending_at field
• 👀 [Dashboard] Added interacted metadata to the guide message log timeline
• 🐛 [Dashboard] Fixed the width of the HTTP channel button in the workflow step pane
• 🐛 [Dashboard] Fixed the callout UI within Deactivate workflow modal

Today we're releasing a significant improvement to our CLI with the ability for any user to log in via their Knock account.

Previously, in order to use the CLI, you would have to use a service token to authenticate. Service tokens are great for non-local, shared environments, like when using Knock inside your CICD pipeline. However, for engineers who want to work with their Knock resources locally, requiring them to create a service token was an unnecessary extra step.

Now, Knock users can simply knock login to gain access to the CLI and get started managing their Knock workflows, templates, and more in code. You'll be redirected from the CLI to your browser to authenticate and grant access to your Knock account. Users who have authenticated with the CLI will then be granted the same permissions they have in the dashboard.

We’re excited to make it even easier for you and the engineers in your organization to work with Knock locally via our CLI. You can read more and get started today via the docs.

Fixes and improvements

• 🐛 [Dashboard] We fixed an issue where resetting a variable could set the variable to an empty string, causing the default to not be applied.
• 🐛 [Dashboard] We fixed an issue with casing of custom fields during CSV upload mapping.
• 👀 [SDK] We've added the ability to opt out of inline-identify in the JS and React SDKs.

Today we're releasing support for sending push notifications via Amazon's Simple Notification Service (SNS). Previously, if you wanted to send push notifications you would have to setup a direct connection with FCM or APNS, or use OneSignal or Expo.

Now, with our support for Amazon SNS you can route push notifications from Knock through Amazon's SNS infrastructure. Our SNS integration even has support for automated deregistration should the user's device token no longer be valid.

You can read more in our integration documentation, or can get started today using Amazon SNS by creating and configuring it as a channel within your Knock account.

Fixes and improvements

• 🐛 [Dashboard] We fixed an issue where the "Request access" button for the APNS + FCM channel group was causing an error.
• 🐛 [Dashboard] We fixed an issue where accessing the conditions builder could cause the application to error in certain situations.
• 🐛 [Dashboard] We fixed an error where the template changes toast message would appear erroneously when expanding or collapsing variables in the state pane.

Today we're releasing our Knock-powered default email channel, giving all new Knock accounts the ability to start sending emails, without needing to setup a third party provider.

Using the new Knock-powered email channel, you'll be able to send up to 100 emails from your Knock account per-month for free, perfect for testing or for small side projects. The limit is per-account, so includes both your development and production environments. Once the monthly limit is reached your messages will stop being delivered until it's reset on the first of the month.

You'll find the new Knock-powered default email channel waiting for you once you create a new Knock account. From there, you can select the channel as you're building your workflows or broadcasts to start sending emails to your users.

Fixes and improvements

• 🐛 [Dashboard] We fixed an issue with broadcasts where if your broadcast contained channel steps under a branch, the broadcast would be marked as invalid.
• 🐛 [Dashboard] We fixed an issue where the tenant in the autocomplete in the template editor would not display any custom properties.
• 🐛 [API] We fixed an issue where a schedule couldn't be created for a tenant.
• 🐛 [Notification engine] We fixed an issue where SMS to overrides were not being respected.
• 🐛 [SDKs] We fixed an issue where some fields on the Message schema were not correctly marked as required.

Today we’re releasing a revamped dashboard sidebar, making it easier than ever to work with Knock. As we’ve added more features and sections to the Knock sidebar, many of you have told us that it’s difficult to find your way around.

With our new, reworked information architecture, we’ve made it easier than ever to find what you need in the Knock dashboard, and to move across the environments you have configured within Knock.

We’ve also gone ahead and moved a few items into the “Settings” page, so they’re better classified as what they are. You’ll find that we also gave the sidebar within the setting section on your account an overhaul to better logically group different areas.

All of these changes have rolled out to all users today.

New sidebar with sections

The new sidebar groups related areas into clear sections and keeps primary actions in reach. Workflows, Broadcasts, and Commits sit at the top for quick access, while Content, Recipients, Observability, and Platform organize the rest. You can collapse sections to reduce noise and stay focused.

Top-level environment switcher

The environment switcher now lives at the top of the dashboard, visible on every page with a new, refreshed look.

New settings page

Settings have a new left sidebar that groups controls by account, version control, integrations, and admin. Channels, Integrations, and Sources now live here under integrations, so provider setup and data connections sit alongside the rest of your workspace settings.

New account dropdown

The account menu is streamlined with quick access to your settings, channels and sources page, accounts, and sign out. Organization switching is easier to see and faster to use.

New help menu

The help menu provides quick links to docs, API reference, and our Slack community. You can also share feedback and contact support in one click.

Fixes and improvements

• 🐛 [Dashboard] We fixed a variety of small issues that would cause the dashboard to error.
• 🐛 [SDK] We fixed token signing in Cloudflare Workers.
• 👀 [Dashboard] When creating new channel step, the selection will default to your email channel when there is only one.
• 🐛 [SDK] We fixed a bug when listing users in the Node SDK.
• 👀 [Dashboard] We added filters to the Broadcast messages log.
• 👀 [Dashboard] The CMD+DEL shortcut no longer deletes the entire block in the template editor.
• 🐛 [Dashboard] We fixed a bug when trying to select a different webhook channel.
• 👀 [SDK] Microsoft recently deprecated multi-tenant bot registration, so we now support sending notifications as Microsoft Teams bots registered with Azure as single-tenant.

Today we're excited to introduce a completely rebuilt CSV uploader that makes it faster and easier than ever to upload users for broadcasts, with a powerful new feature that lets you include ephemeral data that won't clutter your user schema.

Lightning-fast uploads with instant feedback

We've rebuilt the CSV uploader from the ground up with performance in mind. The uploader now opens instantly and processes uploads in seconds, giving you real-time feedback as users are added to your broadcast or audience. You'll see the user count update live as your file is processed, making it easy to track progress and confirm your upload is working as expected.

Streamlined column mapping with full control

The new mapping interface gives you complete control over your data. You can easily add new columns, rename incoming columns, or skip unnecessary ones. This flexibility means you can work with any CSV structure without having to modify your files beforehand.

Per-recipient broadcast data

Here's the game-changer: when uploading users for a broadcast, you can now categorize CSV fields as either "user data" or "broadcast data". User data gets saved to your user schema as usual, but broadcast data is used only for that specific broadcast.

This is perfect for including one-time information like:

• Promotional discount codes unique to each recipient but not necessary to reuse
• Event-specific details like seat numbers or session times
• Usage metrics relevant only to that broadcast

Previously, if you wanted to include this type of data in your broadcasts, you'd have to store it permanently on your user records with no easy way to clean it up later. Now you can keep your user schema clean while still personalizing broadcasts with rich, contextual data.

Save uploaded users as reusable audiences

When uploading users to a broadcast, you still have the option to save them as a new audience that can be reused for future broadcasts. This makes it easy to build and maintain audience segments without having to re-upload the same users repeatedly.

Fixes and improvements

• 🐛 [In app feed] We fixed an issue where the realtime feed didn't update after marking all archived.
• 🐛 [CLI] We fixed a regression with the push all command in the CLI.
• 🐛 [Dashboard] We fixed an issue where searching for a source event with a space would return no results.
• 🐛 [Dashboard] We fixed an issue where setting user preferences in the UI would fail even though setting via the API worked for the same payload.
• 🐛 [Dashboard] We fixed an issue where workflow categories with spaces would break.

Today we’re excited to share a new Changes tab on every versionable resource in the Knock dashboard and an improved commits experience.

New tab for resource-specific version control

On versionable resource pages, we introduced a new tab titled "Changes". This tab gives you a more detailed view of the changes you've made to your resource. You can see the changes you've made, the commits that need promoting, and a history of when your resource was last promoted.

You'll also be able to see the historical commits for that resource, enabling full visibility into the changes that have been made to your resource over time.

Commit and promote changes directly from any resource

We've added the ability to commit and promote changes directly from any resource. This means you can now make changes to a workflow, email layout, or any other versionable resource and commit those changes without leaving the page. The new commit flow provides a clear summary of your changes and lets you add a descriptive message before committing.

Once committed, you can promote those changes to the next environment too, right from the resource page. This streamlines the process of moving changes through your environments.

View changes across environments

The new changes tab also enables you to view the overall status of your resource across environments. Previously, it was difficult to know when a resource had unpromoted commits in other environments. Now, we have a special indicator that introduces a visual cue to help you identify when a resource has uncommitted changes or unpromoted commits in other environments.

And when a resource is synchronized across all environments and in production, you'll see a green checkmark to indicate that the resource in its current state is live in production and the same across all environments.

Fixes and improvements

• 🐛 [MCP] We fixed an issue where creating a new partial from the MCP server crashes partials list.
• 👀 [Dashboard] We added filtering for messages under users/tenants/objects.
• 👀 [Dashboard] We improved the translation editing experience.
• 👀 [Dashboard] Introduced breadcrumb navigation for the dashboard.
• 🐛 [Dashboard] We fixed an issue where previewing a message would mark it as "read" inadvertently.
• 👀 [Docs] We added Guides tooling to the Agent Toolkit docs.
• 👀 [SDK] We added a usePreferences hook to the React SDK.
• 🐛 [API] We fixed an issue with plaintext link parsing.