Slack two-way sync
Slack two-way sync for RyTask is planned — /task capture is live today; mention capture, status and comment sync to threads, and low-noise alerts come next.
What works today: the /task slash command creates a RyTask item from Slack in
seconds, a guided modal helps you fill in the details, and you get an ephemeral
acknowledgment with a link to the new item. See the Slack guide
for setup and usage.
This page covers the rest of the planned Slack story (differentiator D2): making Slack a true two-way surface rather than a one-way capture funnel. The aim is to keep the conversation and the work connected — without turning your channels into notification noise.
What's planned:
- @bot mention capture — mention the bot in a thread to turn the conversation into a task (MVP scope).
- Two-way sync — status changes and comments flow back to the originating Slack thread (MVP scope).
- Smart, low-noise notifications — inform without spamming the channel (MVP scope).
- Channel-to-project routing — map Slack channels to RyTask projects for intake (v2).
Outbound webhooks
Outbound webhooks for RyTask are planned — subscribe a URL to item, comment, and time events for signed, retried payloads, with a delivery log you can replay.
Roadmap (coming soon)
One page per planned capability cluster — what RyTask intends to build, with tiers, and nothing pretending to be shipped.