Hey team! 👋 I'm building a daily Slack triage workflow using the API gat

Ideas / Feedback
1

Hey team! :waving_hand:

I’m building a daily Slack triage workflow using the API gateway and hit a small blocker. The current Slack OAuth connection supports reading messages (channels:history) and sending DMs (chat:write), but lacks the channels:write scope needed for conversations.mark.

Use case: Automated triage bot that:
Scans 200+ channels for @mentions and action items
Marks low-priority channels as read when nothing needs attention
Surfaces only actionable items to reduce noise

Scope needed: channels:write, groups:write, im:write, mpim:write (for completeness)
Impact: Enables “inbox zero” automation workflows — a common pattern for exec/engineering leaders using Maton.

Any chance this could be added to the Slack app configuration? Happy to test or provide more context. Thanks!

2

Hey, sorry for the delay, I updated the Slack integration to include the scope required for conversations.mark, so it should be good to go now. You need to delete your existing connection and recreate it to authorize for additional scopes. I also updated the slack skill to be more comprehensive in both api-gateway skill and slack-api skill: