Write the stand-up where you already are, press the shortcut, pick the channel. And when the thread is the thing you need, pull it into your work session so the next agent answers with it in hand.
Post to Slack is on out of the box because it's the row that saves the trip. The three pull rows are opt-in, because a channel you drag into your work session should be a decision rather than a habit.
Both trips cost the same thing: opening Slack, which is never a two-minute visit. These four cards are what the connection removes, and the one caveat it won't hide from you.
Post an update to any channel, or pull a channel, a thread or a search into your session. Search is the one row that needs a user token: Slack doesn't grant message search to bots, and the card says so rather than failing quietly.
What you posted is logged as a session entry once Slack confirms, so the next agent runs knowing the team was told.
Post to Slack is a workflow step, and a parallel step dispatches two to four destinations at once. Branches are best-effort: a message that landed stays landed, because it can't be un-sent.
Turning the card off hides the rows and stops workflows using it, while the token stays for an instant reconnect. Forget credentials is the separate, deliberate clear.
The app is yours, not Khint's, and it carries the three scopes you granted it. There's no event subscription and no background read of your workspace.
Security and privacySlack asks for a small app of your own. It's the longest setup of the six, and it's four screens.
At api.slack.com/apps, choose From scratch and pick your workspace.
Under OAuth & Permissions, add chat:write, channels:read and channels:history. That's everything the posting and pulling rows need.
Install the app to your workspace and copy the Bot User OAuth Token. It starts with xoxb-.
Paste the token, Save, then choose your default channel. The token goes into your operating system's keychain.
Slack doesn't grant message search to bot tokens. If you want Search messages, paste a user token (xoxp-) rather than the bot one. The other three rows work on either.
An integration is where work comes in and goes out. These three are what happens in between.
It depends on your workspace. Creating an app and installing it to a workspace can require admin approval on some Slack plans, and on others any member can do it. The app itself is yours, asks for three scopes, and isn't a Khint-owned app: nothing is shared with us.
Because Slack doesn't expose message search to bot tokens at all. It's a user-token API. If you want that row, paste a user token (xoxp-) instead of the bot token (xoxb-). Posting and the two pull rows work with either.
No. It calls Slack only when you press a row. There's no event subscription, no polling and no copy of your workspace anywhere: what a pull brings back lands in your local Memory session, which never syncs.
The Slack call is free. If the row hands your text to an agent to rewrite it into an update first, that's one normal agent run against your monthly credits. Posting a selection as-is, and every pull, cost nothing.
Yes. A workflow's parallel step takes two to four destinations and dispatches them concurrently from the same running text, so a single press can file the ticket, publish the page and post to the channel. Branches are best-effort: the ones that succeeded stay, because a landed message can't be un-sent.
Free with 300 credits a month. No credit card. macOS 13+ or Windows 10 22H2+.
Post to Slackwrite
Create issue
Publish page
SlackPaused
