Turn Slack threads into content ✏️

Hello everybody, welcome back to Moodboard 🌴

Somewhere in your company's Slack right now, there's a thread that would make a great newsletter or LinkedIn post.

A smart question, a few sharp answers, maybe a real example with real numbers. But in about 48 hours it'll scroll away and nobody will ever see it again.

Today, we're showing you how to build a Zapier automation (a simplified version of a workflow we build for a lot of our partners at Tailwind) that turns that Slack gold into engaging content.

You drop a question in Slack, your team answers it, you react to the message with an emoji, and a newsletter draft lands in your inbox.

Let's get into it 👇

The Workflow

Here's what this looks like in practice:

1. Drop a question in a Slack channel. Something your audience would actually want answered. "What's the biggest mistake you see clients make with cold email?" or "What changed in our onboarding that cut churn?"
   

2. Let your team answer in the thread. No special formatting needed. Just people sharing what they know.
   

3. React to the original message with your trigger emoji. We use "✏️”. This is your "turn this into content" button.
   

4. Zapier grabs the whole thread, sends it to Claude, and delivers a draft. To your DMs, a Google Doc, or right in the same Slack thread.
   

The nice thing about this system is that all your team has to do is answer questions like they already do. The automation formats that insight as an engaging newsletter.

The Build

This is a 4-step Zap. Here's the build:

Step 1: The Trigger

Slack → New Reaction Added

Configure it to watch for your chosen emoji (✏️) in your chosen channel.

This means the Zap only fires when you decide a thread in your specified channel is newsletter-worthy. No noise, no accidental drafts from random conversations.

Step 2: Extract the Thread Content

Slack → Retrieve Thread Messages

This step grabs the original question plus every reply underneath it. That full thread is the raw material for your draft.

Step 3: Draft with Claude

AI By Zapier → Send Message

This is where the transformation happens. Create an “AI by Zapier” block, specify your model of choice (I’d go with Claude Sonnet 5, at least), and tell it what you’re trying to accomplish.

Here’s how I’d configure the instructions:

You are a newsletter writer. You turn internal team discussions into polished newsletter drafts for an external audience. Write in short, conversational paragraphs (1-3 sentences each). Preserve specific examples, numbers, and stories from the discussion. Remove internal references, employee names, and anything confidential. Do not invent information that wasn't in the thread. No corporate jargon, no rhetorical questions, no em dashes.

Turn the following Slack thread into a ~300-word newsletter draft. The first message is the topic/question. The replies are the raw material.

Structure:

- Open with a hook (the most surprising or useful insight from the thread)

- 2-3 key takeaways from the discussion, each explained in plain language

- One concrete action the reader can take this week

Thread: [map the thread messages from Step 2 here]

That bracketed part is where you insert the dynamic data from Step 2 using Zapier's field picker (use the forward slash and select the thread messages output called “Result Text”).

Step 4: The Delivery

Send the draft wherever it's most useful for your workflow:

• Slack → Send Channel Message (draft lands in the same thread)

• Google Docs → Create Document (ready for editing)

• Gmail → Send Email (lands in your inbox)

We like the Slack DM route because the draft comes right back to where you already are, while the conversation is still fresh in your mind.

Systemize It

A few things worth knowing before you set this loose on your team:

The draft is generally ~70% of the way there. Expect to spend 15 minutes editing (still a massive head start over a blank page).

Seed the questions deliberately. The draft is only as good as the thread you feed it. Ask specific, contained questions your audience is actually curious about, not vague open-enders.

Customize the voice. Once you've got a few editions published, paste 2-3 of them into the System Instructions as style examples. The drafts will start sounding a lot more like you.

This works beyond Slack. The same pattern (capture where the work happens, transform with Claude) applies to meeting transcripts, sales call recordings, and email threads. Slack is just the easiest place to start because the trigger is one emoji.