SMS recipient override

Today we're announcing support for overriding the recipient of an SMS message. This is useful if you want to send an SMS to a different user than the one that triggered the workflow.

With the new SMS recipient override, you can now specify either a static or dynamic value via Liquid for the recipient of an SMS. For example, you might be sending an SMS to the user, but be sending it to the new phone number they entered and stored on the recipient profile as recipient.new_phone_number.

You can read more about SMS overrides in our documentation.

Fixes and improvements

  • 👀 [Dashboard] You can now see environment.merged_latest changes in the audit logs.
  • 🐛 [API] We fixed an issue where hourly schedules with an interval > 1 would be enqueued at the wrong time.
  • 🐛 [Dashboard] We fixed an issue where the workflow builder would show an incorrect tooltip when adding steps.
  • 🐛 [Dashboard] We fixed an issue where after adding an integration, you would need to refresh the page to see it show up in the workflow builder.
  • 🐛 [SDK] You can now safely mount the <KnockProvider> in the React SDK with a null or undefined userId.