Set inline channel data and preferences

We've expanded our workflow trigger inline identify to support setting channel data and preferences for recipients. That means it's now easier than ever to start sending notifications to your users with Knock, without the need to backfill existing data. It even works for setting data for multiple channels and for per-tenant preferences too.

Read more on setting channel data inline and setting preferences inline in our documentation.

Conditions builder improvements

We've added a whole host of new features to our step and channel conditions builder this month. You can now reference:

  • Environment variables (e.g. skip this step if we're in the development environment)
  • Workflow run state including total_activities and total_actors (e.g. only execute the step if we have more than one item from a batch)
  • The current tenant (e.g. only batch for workspace X and never for workspace Y)
  • The current workflow (e.g. only send to SMS if the workflow category includes messages)

Read more in our docs.

Fixes and improvements

  • 👀 We expanded the delay block to support dynamic delays from the recipient, actor, environment and more
  • 👀 We added the ability to reference the in your notification templates to get access to the unique, recipient-specific
  • 👀 We moved 'Designing workflows' to its own section in the documentation
  • 👀 We made improvements to our email previews to be more consistent with what's sent
  • 🐛 We fixed an issue where JSON values in chat templates would not escape \n and \ characters correctly
  • 🐛 We fixed a bug with mailgun delivery checks where the requests would timeout after 5+ seconds
  • 🐛 We fixed an issue where some starter plans could not create a new webhook
  • 🐛 We fixed a bug where blank in-app feed messages would fail to send