CoDesk and Slack
Find the decision, the request or the promise that lives in a channel nobody thought to write down.
What it reads
- Messages in the channels you choose to connect, and nothing in the ones you do not
- Threads, so a reply keeps the question it answered
- Who said what, and when
- Links and files shared in those channels
Only ever what the credentials you supply can already see. Connecting Slack does not widen anyone’s access to it.
What you can ask once it is connected
- “What did the client actually ask for last week?”
- “Where did we land on the pricing question?”
- “Has anyone replied to Dana?”
- “What was raised and never picked up?”
Better with a second tool
Most questions worth asking cross two systems. Slack pairs particularly well with:
- Jira — “Was the extra work ever filed, or only asked for?”
- QuickBooks — “Who is chasing the overdue invoice, and what did they say?”
- Fireflies — “Does the thread match what we agreed on the call?”
What it can change
Slack message drafting is in development. When it lands it will work the same way Jira does: CoDesk prepares the message, you read it, and nothing is sent until you approve it. Until then CoDesk reads Slack and does not post to it.
What connecting it needs from you
A Slack app installed to your workspace, with read access to the specific channels you pick. Private channels stay private unless you deliberately add them. You can remove a channel at any time.
Next
See every tool CoDesk connects to, read how a question becomes an answer, or ask us whether your setup fits.