Tightknit Release Notes: Gamification Notifications and API Updates
@here
🔔 Gamification Admin Notifications
Journeys have been released into the wild in so many workspaces—users are completing Journeys and earning Badges left and right. We couldn't be more excited to follow along with the progress, and we know you are too! That's why we've added two more notifications in the Team Notifications modal: Badge Received and Journey Completed. Now you can receive a notification in your Tightknit Hub Channel each time your members earn one of these achievements. If you no longer want to receive these updates, simply uncheck them in the Team Notifications modal in your Community settings.
Updates:
[Slack] Added new Team Notification options for when users receive a badge and when users complete a journey
[Slack] Polls can now be managed using the Manage Content message shortcut from Tightknit
[API] Added pagination to the Events List GET API
[API] Implemented Slack notifications for the Create Event API
[API] Updated the Events webhook payload shape to align with the REST APIs. The status field has been removed. The action field will have a value of 'calendar_event.user_registered' and 'calendar_event.user_unregistered' for user event registrations an unregistrations, respectively. ⚠️ This is a breaking change.
[API] When the Event Attendee update API is used to add a personal join link, and the current time is during the event, a notification is sent immediately to the user
Fixes:
[Slack] Non-admin users are now prevented from approving and publishing events that are up for review in the Tightknit Hub channel
[Companion Site] The event link on the Event detail page now opens in a new tab
[API] Fixed bug where validation failed to work properly if the Content-Type header was missing from the API request
