The idea is:
Introduce the ability for the Slack Trigger to filter events based on bot_id or app_id directly in the trigger options, and fix issues with Slack File Upload functionality.
My use case:
- Slack Trigger Filtering: When an AI bot sends a message into Slack, it unintentionally triggers the same workflow the message originates from. The current workaround is to filter these events after the trigger, but this still counts as an execution, effectively doubling the execution count and creating inefficiencies.
- Slack File Upload Issue: The Slack File Upload functionality is critical for sending audio or other files to Slack, but it currently does not work, even when using HTTP nodes. Slack’s updated File Upload process has introduced complexities that make it difficult to set up effectively.
I think it would be beneficial to add this because:
- For Slack Trigger:
- Filtering based on
bot_idorapp_iddirectly in the Slack Trigger would eliminate unnecessary executions, saving on execution costs and improving workflow efficiency. - It would simplify workflows by removing the need for additional filtering nodes after the trigger.
- For Slack File Upload:
- File uploads are essential for workflows that require sharing audio, images, or other types of files directly into Slack.
- Fixing the File Upload issue would restore this functionality and enable seamless integration for workflows that depend on sending media to Slack.
Are you willing to work on this?
With Pleasure!