Use Slack with an AI Browser for Content Planning

If you use Slack and you regularly need to plan the next content cycle, the bottleneck is usually the same: Slack holds part of the context, but content planning also needs signals that live outside it - on the public web, in LinkedIn, in news, in other connected apps. Strawberry is built to combine the Slack context with the rest of the browser, and run the full workflow as a companion you can re-trigger every week.

This page describes specifically how Strawberry handles content planning when Slack is one of the inputs. It names the Slack surfaces involved, the signals the workflow actually needs, an example prompt you can paste, and what a good output looks like.

The job a content marketer, founder writing for the company, brand lead is trying to do

The goal of content planning is to decide what to publish next week and why, with each piece tied to a specific search query or audience. The success metric is concrete: ratio of published-to-planned > 80%, average time-on-page above 2 minutes, organic traffic up week over week. That definition matters because it shapes what Slack needs to contribute to the workflow.

What signals content planning actually needs

For each signal below, here is whether Slack can contribute directly or whether Strawberry has to find it via the browser:

• Current search rankings and traffic - Slack does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Competitor content gaps - Slack does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Questions the sales team gets repeatedly - Slack does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Internal subject-matter expertise - Slack does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Seasonal or event-driven hooks - Slack does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Internal data the team could publish - Slack does not contain this directly. Strawberry uses the browser plus public sources to fetch it.

What Strawberry can do inside Slack

Strawberry can read recent channel activity, summarize a thread, and post approved updates back to a channel.

Slack surfaces Strawberry uses for this workflow: channels, DMs, threads, saved items, user list.

How Strawberry runs content planning with Slack

1. Strawberry opens the Slack channels that contains the relevant context.
2. The companion pulls related context from Slack (DMs, history, attached files) where it exists.
3. For the parts Slack does not store, Strawberry uses the browser - web search, LinkedIn, news, the prospect's website.
4. Strawberry synthesises the output in the shape this workflow needs: A content calendar with each row.
5. A human reviews before any external action (send, update, post). Then the approved output is saved back to Slack or your system of record.

Example Strawberry prompt

Paste this in a new Strawberry chat with Slack connected. Adjust the specifics to your actual ICP, role, or topic.

Read this Slack channels and any linked context.
Then run a full content planning workflow on it. Use the browser to fill any gaps not in Slack.
Return the output in the shape we use for content planning: A content calendar with each row: target keyword/audience, format, hook, draft owner, due date.
Do not send anything externally. Save the draft to me to review.

What a good content planning output looks like

Here is what a finished output for content planning should look like in practice. The specifics will change for your use case, but the shape should look similar:

• Week 24 - Content plan
• Mon: comparison post 'Strawberry vs Manus' - target 'manus AI alternative' - draft by Laurits - publish Tue
• Wed: customer story Iltihouse - target 'AI for outbound sales' - draft by Lotte - publish Thu
• Fri: weekly product release recap - target loyal users + Github watchers - draft by Charles - publish Fri

Why Slack for this, and where to use a different tool

Slack is strong for this workflow because Strawberry can read recent channel activity, summarize a thread, and post approved updates back to a channel.

Where Slack falls short Sending in Slack requires explicit approval; private channels need explicit invitation; search retention depends on plan.

Consider also a CRM or project tool for tracked follow-up.

Common mistakes when running content planning

• Planning content nobody actually searches for
• No internal owner so the calendar slips week after week
• Writing about generic topics where the team has no edge

Connecting Slack to Strawberry

Native OAuth, read + write scopes are separate. Once connected, the companion can read the surfaces above without re-authenticating, and any write action still requires explicit human approval the first time the workflow runs.

Caveats

Do not let any AI agent send emails, update CRM records, or change shared systems without a clear approval step. Strawberry is strongest when the workflow combines browser context with connected-app context and a human review for sensitive actions.