Email-based user ID resolution for Slack
Today we’re introducing email-based user ID resolution for Slack, simplifying the steps needed to send direct messages via Slack to your Knock users.
Previously, if you wanted to send a direct message via Slack to one of your users, you needed to update your Knock user’s channel data to include their Slack user ID. This ID is typically found by making a request to the users.lookupByEmail endpoint of the Slack API using your Knock user’s email address.
Now, Knock can automatically make this API request on your behalf before sending a message. When the request succeeds, Knock will automatically add the Slack user ID to the user’s channel data.
You can read more about enabling email-based user ID resolution for Slack in our documentation.
- 👀 [Dashboard] We made it possible to see who created a workflow, in addition to who last edited a workflow.
- 🐛 [Notification engine] We fixed a bug in which temporary failures from Mailgun were treated as undelivered.
- 🐛 [Dashboard] We fixed a bug in which a cloned workflow would default to the inactive state.
- 👀 [SDK] We updated our SDKs to include
ending_atfor scheduled workflows.
