This is a nuanced but important edge case — when a long bot message gets split by Slack into multiple sequential messages, each fragment fires its own trigger, which turns a single conversation into a flood of separate Taskade projects. Deduplication or message-grouping logic would fix this cleanly.

We just launched our Integrations Directory in v6.97.0 with detailed trigger and action documentation at https://taskade.com/integrations, and in v6.104.0-v6.105.0 we introduced MCP Connectors, a new architecture for managing third-party tool connections that gives us much more control over how we handle incoming data streams. That infrastructure opens the door to smarter batching and deduplication logic for sources like Slack.

As a workaround in the meantime, you might consider filtering triggers by message author type (bot vs. human) or setting a delay on the automation to catch grouped messages. We've noted your specific use case around bot-generated split messages — it's a legitimate gap we want to address properly. Thanks for the clear write-up!

This is in development and your votes helped us prioritize it.

Follow our progress: Changelog | Product Updates

Thanks for your patience and for helping shape Taskade!

This is in development and tracked on our roadmap. Your votes helped prioritize it.

Follow our progress: Changelog | Product Updates

Hello,

To better understand your request, could you please provide more details on what you want restricted? Are you referring to consolidating multiple messages into a single task or project, or are you suggesting a restriction on only accepting messages from specific users?

Your clarification will help us address your request more accurately. If you have additional information or specific requirements, please feel free to share.