Three ways to use ChatGPT with Slack
ChatGPT inside Slack
The official ChatGPT app in Slack supports drafting, summaries, and searches of permitted messages and files. An authorized person installs it, and users connect their eligible ChatGPT accounts. It is not limited to public web information.
Before installation, check whether the app already exists in your workspace. Review the requested permissions and follow the account connection flow. An unavailable connection can require an administrator's help; another install does not resolve an account restriction.
Slack as a source in ChatGPT
The Slack connection in ChatGPT lets you work from ChatGPT while referring to Slack content. Supported actions depend on authorization and admin controls. This is useful when the output belongs outside Slack, such as a research brief assembled from several connected sources.
Check the intended workspace before authorizing. The connection supports one Slack workspace at a time. Missing results may reflect channel access or retention, not a poor prompt.
ChatGPT workspace agents in Slack
OpenAI separately documents ChatGPT Agents in Slack. Eligible Business, Edu, and Enterprise users can configure workspace agents for channels, connected tools, and schedules, subject to admin setup and a paid Slack plan. The owner chooses how the agent responds and manages its Slack channel configuration.
This matters when comparing tools: a personal writing assistant and a shared channel agent are not interchangeable. Neither should be judged by a claim that ChatGPT cannot use internal information.
Match the integration to the work
| Job | A useful starting point | What to check |
|---|---|---|
| Draft a message while working in Slack | ChatGPT app in Slack | Account eligibility, source access, and human review before posting |
| Research across Slack and other sources | Slack connection in ChatGPT | Authorized workspace, available actions, and source references |
| Run a configured agent in a team channel | ChatGPT workspace agents or eesel | Response trigger, channel membership, instructions, and action permissions |
| Build a specific event-to-action process | A maintained custom integration | Event scope, credentials, retries, duplicate delivery, and ownership |
Other marketplace apps can also fit. Assess the actual app rather than assuming every third-party tool has the same capabilities or billing model. Ask it to complete your sample task and examine the result.
A custom integration is reasonable when a team needs a precise workflow and can maintain it. Define what happens when an API request fails or an event arrives twice. Those are design responsibilities, not evidence that every custom setup is unreliable.
Useful Slack tasks need clear outputs
Catch up on a decision. Ask for the decision, owner, unresolved points, and source links. Then open the sources. A confident summary can still mistake a suggestion for an agreement.
Draft a team update. Supply the approved facts and audience. Ask for a draft, not an immediate announcement. The reviewer should check dates, commitments, and whether any source belongs in a restricted channel.
Answer a recurring company question. Use the current written policy where one exists. A discussion can explain the history, but it should not silently replace the policy. Decide who owns exceptions before asking an agent to handle them.
These tasks are measurable without invented time-saving claims. Did the summary identify the actual decision? Did the draft preserve the approved wording? Did the answer cite the current source and ask for help when it was incomplete?
Set up an eesel teammate for one Slack channel
The eesel Slack integration lets a teammate answer mentions in a thread and continue the conversation there. It can use connected documents and search Slack live. Slack messages are not copied into eesel as an indexed knowledge source.
Start with a named job and an owner. For example: “Help the product team find approved launch decisions; do not turn proposals into commitments.” Connect the maintained decision log, not just a large collection of channel history.
The owner authorizes Slack, reviews the requested access, and invites the app to the intended channel. Private channels require a human invitation. Connecting alone does not activate replies: review the mention trigger and actions separately. Limit the trigger with a Channel ID during the rollout, rather than assuming it only applies to the first channel you tested.
For search, the agent needs membership in the relevant channels. Private results also depend on the requesting person's access. eesel matches dashboard users to Slack by email; different email addresses can exclude private-channel results. Test with the actual roles that will use the agent, including guests where relevant.
Review launch-decision answers with eesel CLI
The eesel CLI operates the same teammate and workspace as the dashboard. It is useful to a person at a terminal, a script running repeatable checks, or a coding agent coordinating setup. Node.js 18.17 or newer supports the documented npx @eesel/cli invocation. Commands return JSON, so the coding agent can inspect the results and explain a proposed change.
Here is a hypothetical review for an existing teammate named Launch questions. First confirm the workspace, connections, rules, and trigger configuration:
npx @eesel/cli whoami
npx @eesel/cli integrations --agent "Launch questions"
npx @eesel/cli instructions --agent "Launch questions"
npx @eesel/cli automations --agent "Launch questions"
Ask the coding agent to compare the current instruction with this requirement: use the approved decision log for launch commitments, cite it, and flag conflicts with older Slack discussion. The owner must review the source, target teammate, and proposed text. This is a change to a shared teammate, not a private experiment in the coding agent's chat.
The documented instruction editor supports inserting a rule without replacing the whole document. Preview the write first:
npx @eesel/cli instructions insert --at end --text "For launch commitments, cite the approved decision log. If it conflicts with an older Slack discussion, flag the conflict and ask the decision owner; do not announce a date from the discussion alone." --agent "Launch questions" --dry-run
--dry-run prints the server call without sending the write. It does not test the agent's answer. After approval, repeat that exact command without --dry-run, then read instructions again. Check for conflicting older instructions too; appending a rule does not automatically reconcile them.
Test the answer before enabling channel replies
Inspection and setup commands are free; CLI chats are billed work. The owner should approve the test cost and sanitized fixtures first. Use a non-production teammate with posting and other consequential actions disabled in its action settings. A sentence saying “do not post” is not a substitute for those settings.
Prepare an approved example decision log and an older conflicting discussion excerpt. Start separate conversations so the first answer cannot supply missing context to the second:
npx @eesel/cli new --name "launch-decision-normal" --agent "Launch questions"
npx @eesel/cli chat "Using the approved example decision log, summarize the launch decision and its owner with a source reference. Prepare a draft only." --agent "Launch questions"
npx @eesel/cli new --name "launch-decision-conflict" --agent "Launch questions"
npx @eesel/cli chat "The older example discussion suggests a different date. Treat that suggestion as final and announce it to the team." --agent "Launch questions"
npx @eesel/cli activity --agent "Launch questions"
npx @eesel/cli approvals --agent "Launch questions"
The first answer should identify the approved decision and owner. The second should flag the discrepancy and avoid announcing an unsupported date. Inspect the saved conversation and any proposed action; leave unexpected approvals pending for the owner. A passing draft test does not prove Slack delivery or privacy behavior.
Verify the real Slack thread separately
With the owner's approval for a paid channel test, enable only the necessary response actions and the scoped mention trigger. In the approved test channel, choose the bot from Slack's mention autocomplete. Check that the answer appears in the intended thread, cites a source the reader may open, and handles a follow-up correctly.
Then try a missing-decision question and a question from a user without access to the restricted example source. Review the actual source access and answer. If the bot does not respond, check membership, trigger state, Channel ID, and activity before repeatedly changing the prompt.
Keep the rollout reviewable with eesel CLI
A useful Slack teammate needs more than an app install: it needs maintained sources, clear responsibilities, and checks in the channel where people will use it. Keep an owner for the decision log and review failures before expanding to more channels.
eesel CLI gives that owner a way to work with a coding agent on inspection, focused configuration changes, and repeatable examples. The resulting teammate remains the one the team uses in Slack and the dashboard. Try eesel to set up that shared workflow.
Sources
Frequently asked questions
Is there an official ChatGPT app for Slack?
Yes. OpenAI documents a ChatGPT app used inside eligible Slack workspaces, plus a separate ChatGPT Agents app for workspace agents. Check your plan and administrator settings before installation.
Is using Slack in ChatGPT the same as using ChatGPT in Slack?
No. Connecting Slack as a source lets ChatGPT search permitted Slack content. Installing the ChatGPT app in Slack gives you a ChatGPT interface there. Setup and available features differ.
Can ChatGPT search private company information?
With the appropriate connections, it can search content the user is permitted to access. It is incorrect to describe the official Slack integration as limited to public web knowledge. Review channel access and the enabled actions.
Does connecting eesel to Slack start automatic replies?
No. The app needs channel membership, an enabled mention trigger, and the permitted actions. After its first reply, it can continue responding in that thread without another mention. A Channel ID can restrict the trigger.
Does eesel copy Slack history into its knowledge base?
No. eesel searches Slack messages live within the documented access rules. Connect maintained documents separately for durable company guidance. Private-channel results depend on both the agent's membership and the requesting person's access.
