📚 Intermediate: Contents (8/8)
  1. Build your first web page with Codex
  2. How folders, files, and HTML fit together
  3. Change an existing page the way you want
  4. Read errors and fix them with Codex
  5. Connect Google Drive and search your first doc
  6. Connect GitHub and choose repository access
  7. Connect Notion and check which pages it can see
  8. Connect Slack and summarize a channel

🔁 Cuts repetitive work

New to AI? Start here → Start 1. ChatGPT vs. Codex: what's the difference?

Last checked: November 10, 2026

Connect Slack and summarize a channel

In one line

Connect Slack and start summarizing channels
A connection that finds messages is different from a bot you call in a channel.

The big picture

Illustration (may look a little different from the real screen)

Checking the Slack workspace and requested permissions
Click the picture to see it larger.

Follow along

In this exercise, you’ll read Slack from inside ChatGPT

You need a Slack workspace account and a practice channel. Availability depends on your ChatGPT plan, region, and admin settings. Setting up @ChatGPT inside Slack for your organization is a separate thing.

Connect your workspace

1. Find Slack in apps or plugins

Make sure the service you’re connecting is Slack, then click Connect.

2. Check the workspace name

If you belong to several teams, choose the workspace that has the channel for this exercise.

3. Review the requested permissions and come back

If your company requires app approval, follow the admin process. It won’t open up channels you can’t already access.

4. Summarize with a specific channel and time range

Ask about a short time range in your test channel. Open the linked source messages and check that it kept decisions and suggestions apart.

Prompts you can copy

Summarize a test channel

Find the discussion in [test channel] on Slack from [start date to end date]. Split it into decisions, still under discussion, and to-dos, with links to the source messages. If you couldn't read the whole period, tell me which part you checked and which you didn't. Don't send any messages or edit existing ones.

Check what was searched

Explain which channels, dates, and search terms the Slack summary above actually checked. Don't conclude there's no related discussion just because there were few results. List the message links I should review in the original.

Where people get stuck

Lots of people get stuck here. Find the one that matches your situation!

Don’t assume it read every single message

Narrow the summary by channel, date range, and keywords. Having it flag periods it couldn’t read and access failures makes reviewing easier.

When testing reading, ask it not to send any messages. Adding @ChatGPT inside Slack follows a separate admin guide.

Quick check: If I connect Slack in ChatGPT, is @ChatGPT inside Slack set up too?

Answer: “No, the organization bot is set up separately”
Reading Slack as a connected source and the assistant inside Slack are set up separately.

Official sources

Next tip

Design your first automation for repetitive work →

I'm stuck here

Stuck while following along? Tell me where. Only the site owner sees this. Leave your email only if you'd like a reply.