🔥 Releases – Klaxoon Board Tables, Wrike API: Webhook Filtering & Payload, Wrike AI Feedback, And More! (11/10/2025)
Выделено
TL;DR: Klaxoon Board users can now create and edit tables natively, and Wrike API webhooks now support advanced event filtering and customizable payloads. Plus, help shape the future of Wrike AI, share your feedback on Community (for Ninjas), meet October’s Contributor of the Month, and celebrate our newest Community Orange and Green Belts!
Feature Updates
- Klaxoon: Tables In Klaxoon Board 📊
Tables are now live in Klaxoon Board, making it easier than ever to organize and present information visually.
What’s new?
- Create tables directly from the Insert menu
- Add or remove rows and columns effortlessly
- Customize line color, thickness, and cell backgrounds
- Add and format text inside cells
- Wrike API: Webhook Filtering And Customisable Payload 🛠️
We’re excited to announce the availability of two major webhook enhancements in Wrike API.
Here's what's new:
Here's what's new:
- Customizable Payloads: Choose which fields - such as title, responsibleIds, status, dates, customItemTypeId, recurrence, and more—are included in webhook payloads.
This means you get exactly the data you need, right when an event happens, reducing unnecessary API calls and processing.
- Advanced Event Filtering: Set precise filters to receive webhooks only when specific changes occur, such as updates to a particular custom field, actions on tasks or projects of a specific Custom Item Type (CIT), or the creation of recurrent tasks.
❗️Please Note:
- Not yet compatible with Wrike Integrate.
- Fully backward compatible - no need to update existing integrations unless there is a need to improve efficiency.
Check out the updated Webhook developer documentation for details.
Community News
- Help Shape the Future of Wrike AI: Join Our Wrike AI Power Hour! 🤖
Javier, Product Manager for Wrike AI, and Andrey, Customer Success Manager, invite you to help shape the future of Wrike AI!
Ahead of the Wrike AI Power Hour on November 19, 2025, explore new features like Wrike Copilot and AI Agents, and help shape our AI roadmap by sharing your feedback here.
Don’t forget to submit your questions for the live session here. For more details and to register, click here. We look forward to your input and hope to see you at the event!
- Wrike Ninjas: We Need Your Input! 🥷
We’re preparing some exciting updates to the Wrike Community platform and are gathering early feedback in our Ninja Forum.
If you’re a Ninja, check out the Community post to share your thoughts on what you love, what’s missing, and what would make our community even better!
- October 2025 Contributor of the Month 🏆
A big round of applause to Amy Hunter, our October Contributor of the Month! Special thanks as well to Ali Moses, choongseng, and Szilvia Becző for their outstanding contributions.
Want to be featured next? Jump into Community discussions and share your expertise - the next winner could be you!
- Welcome New Orange And Green Belts – October 2025 🎖️
A big congratulations to everyone who earned their Green or Orange Belt this month:
Your passion and dedication help our community grow. Thank you for all that you do! 👏
Basudha Sakshyarika Community Team at Wrike Wrike Product Manager Станьте экспертом в Wrike с Wrike Discover
Basudha Sakshyarika Wrike Team member Станьте экспертом в Wrike с Wrike Discover
I love this!
Thank you!! Excited to see how this community grows.
This new feature is almost perfect for our use case — great timing!
I’m wondering if there’s a way to use the new filtering option to exclude certain Custom Item Types (CITs) from triggering the webhook event, rather than only being able to include them.
In our situation, we have a few tasks that use a specific CIT and we’d like those not to fire the webhook. Most of our tasks don’t have any CIT at all, so excluding just one CIT would make things much cleaner.
Perhaps this could be considered for a future enhancement?
Hi Stephen Remillard 👋🏼. Currently excluding CITs is not supported. We can just choose to include relevant CITs.
I can see how excluding specific CITs would simplify your setup, so I’ve shared this as a feature request with our product team for future consideration. 👍🏽
Basudha Sakshyarika Community Team at Wrike Wrike Product Manager Станьте экспертом в Wrike с Wrike Discover
Basudha Sakshyarika Wrike Team member Станьте экспертом в Wrike с Wrike Discover