Slack
Slack to LinkedIn post, from the conversations you pick.
Turn Slack into LinkedIn posts: connect Slack once, read-only, and pick the conversations Sonar may read. About once a week it reads the last seven days of those conversations and nothing else, finds the decisions, wins and lessons worth saying, and drafts LinkedIn and X posts in your voice from them. Nothing publishes without your approval.
What Sonar reads
Your permissions, your pick, seven days.
Sonar connects as you, with read-only permissions, so it can never see a room you cannot. Then it reads nothing until you pick the conversations. Here is exactly what passes through, what stays, and what never does.
Reads
- Only the conversations you picked: public channels, private channels you are in, group messages and direct messages, up to 40. Nothing is read before you pick.
- For each one, the last seven days: up to 80 messages, plus the replies in up to 8 threads. Human messages only; bots, joins and anything under 20 characters are skipped.
- Each message as its author's name, the day and the text, cut at 600 characters.
- As you, with read-only permissions (channel, group, DM history and the member list for names). It can never reach a room you cannot already read.
Does not read
- Any conversation you did not pick, even if you could open it yourself.
- Anything older than seven days.
- Files, images or attachments. Only the text of a message is read; a link becomes its label.
- It never posts, reacts or replies. There is no write permission in the grant, and no bot joins your workspace.
Keeps
- The moments it mined: a title, an angle, one line of detail, and the channel they came from, shown as "Slack: #channel".
- Your pick: the names of the conversations you chose, so the next read knows where to look and the row can show them.
- A receipt of the read on the Slack row in Connected sources: how many messages, from which conversations, and how many moments came out.
- The token Slack issued to you, so next week's read runs without asking you again.
Never keeps
- The message text. The week is assembled into one transient block, mined in a single pass, and discarded.
- Who said what. Author names ride the text into the read so the miner can follow a conversation, and leave with it.
- Any moment past the retention you set, if you set one: 30 days, 90 days or a year.
From a thread to a post
Decisions get made in threads. Posts come from decisions.
A meeting is scheduled; a decision is posted. Slack is where the outcome is written down by the people who made it. An invented thread, run the way yours would be.
01
In a channel you picked
#ops
Kill the weekly all-hands, or cut it to fifteen minutes?
Tuesday · 11 replies in the thread
You: fifteen minutes, agenda posted the night before, or we cancel it that week.
Threads are read, because that is where the conversation is. Bots, joins and one-word replies are skipped; each message arrives with its author's name and day.
02
The moment Sonar keeps
Decision · Slack: #ops
The all-hands went to fifteen minutes with a public agenda
Angle: a meeting nobody can defend gets cancelled; a meeting with a posted agenda has to earn its slot every week.
One pass over the week's messages, then the text is discarded. What stays is a title, an angle, one line of detail and the channel it came from. The people in the thread stay out of it.
03
The draft, waiting
LinkedIn draft · in your voice
We nearly killed our all-hands last week.
Instead we cut it to fifteen minutes and made one rule: the agenda goes up the night before, or the meeting does not happen. Two weeks in, it has happened once.The freshest moments are dealt into your weekly deck as drafts; keep one and it lands on your board. Every moment is also one tap from a draft on Home.
Invented for this page. Look at what is not in it: the names of the people in the thread. The channel name stays in Sonar as the moment's provenance, for your eyes only; the moment and the post say "the team". That is the people rule, written into the instructions every draft is produced under, and it names a member of a Slack channel or DM in so many words.
Set it up
One switch, then you draw the line.
- 01
Open Connected sources
Sign in at app.meetsonar.co and open Settings, Connected sources. On your first day the Connect your week row on Home opens the same list.
- 02
Flip the Slack switch
Slack's consent screen lists read-only permissions on your own account: the history of channels, groups and direct messages you can see, and the member list for names. Choose Allow. No bot is added to your workspace.
- 03
Pick the conversations
Back in Sonar the picker opens on its own. Search, tick the channels, group messages and direct messages Sonar may read, up to 40, and press Save channels. Until you save, nothing is read.
- 04
Let the first read run
The first read starts the moment you save. Moments appear on Home shortly after, each labelled with the channel it came from, and the row's receipt shows how many messages were read from which conversations.
- 05
Keep a draft
The freshest moments are dealt into your weekly deck as drafts in your voice, and every moment on Home is one tap from a draft. Keep one and it lands on your board; schedule it or copy it.
- 06
Change the pick, or run it yourself, any time
The Channels button on the Slack row reopens the picker. About once a week is the cadence; the Sync all button at the top of Connected sources runs every connected source now.
Turning it off is the same switch. Sonar revokes its token with Slack and deletes it, along with your pick and the row's receipt. Moments already mined stay yours to keep or delete in Settings, Intelligence, Moments. Your calendar and your calls have their own pages: Google Calendar and Google Meet. The step-by-step guide is Using Sonar with Slack.
FAQ
Questions about Slack.
The decision is already in the thread. So is the post.
Every other source is one page away on Integrations, and the full account of what is read and kept is the privacy policy. Anything else, ask support or write to hello@meetdistilled.com.