[BUG] Slack connector not seen by /schedule
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
I have created a routine with /schedule to create a digest of the new messages on a slack channel.
In Claude Code under https://claude.ai/customize/connectors the slack connector shows as connected.
I tried to disconnect and reconnect multiple times but it does not help. The routine does not see the connector:
Message from Claude Code CLI: after pasting the screen shot attached.
<img width="1184" height="797" alt="Image" src="https://github.com/user-attachments/assets/d92bd4cb-48dc-43e3-a9b3-8c6f473a2ea4" />
"Good news — that screenshot confirms Slack is properly connected and authorized: "Interactif" status, "Create a draft message" interactive tool allowed, and all 12 read-only tools (including "Read channel messages," "Read thread messages") set to "Toujours autoriser."
So the connection itself is fine. The gap is that /schedule's connector list (generated fresh each invocation) still isn't picking it up — that's either a short propagation delay between claude.ai connectors and the routines/CCR system, or this connector type isn't yet surfaced to routines.
Next step: wait a minute or two, then run /schedule update the SPCt Slack Daily Digest routine once more. If Slack still doesn't appear in the connector list after that, this looks like a platform-side sync gap rather than anything on your end — worth reporting via /help in Claude Code, since the connection is clearly live on the web side."
Waited over an hour and it did not help.
What Should Happen?
The routine should see the mcp server as active and use it.
Error Messages/Logs
Steps to Reproduce
create a schedule with the content :
You are running a recurring daily digest job for the Slack workspace at saispctcommunity.slack.com. You have access to three MCP connectors: Slack (for reading channels/messages and generating permalinks), Google Drive (for reading/writing a markdown log file), and Gmail (for creating an email draft).
Each time you run, do the following:
- Find the existing log file in Google Drive. Search for a file named
SPCt Slack Digest.md. If it exists, read its full content and find the most recent## YYYY-MM-DDdate heading - that date is your cutoff, meaning you should only consider Slack messages posted strictly after that date/time. If the file does not exist yet, this is the first run: use messages from the last 24 hours as your starting scope.
- Scan Slack for key messages. Enumerate the channels you have access to in the saispctcommunity.slack.com workspace. For each channel, fetch messages posted since the cutoff from step 1. From these, identify "key messages": announcements, decisions, important questions/answers, deadlines, links to important resources, or anything a busy stakeholder would want to know about. Skip routine chatter, reactions-only threads, bot/automated noise, and small talk.
- For each key message you keep, gather: the channel name, the author (if available), a short 1-3 sentence summary or relevant excerpt, the timestamp, and a permalink to the message (use the Slack permalink tool, e.g. chat.getPermalink or equivalent).
- Update the markdown log in Google Drive:
- The file should be a running list organized by date, with a
## YYYY-MM-DDheading for today followed by a bullet list of key messages, each formatted like:
- **[channel-name]** (author): summary - [link](permalink)
- If the Drive tools available to you don't support in-place editing, read the full existing content, construct the new full content with today's section added (keep existing sections intact), and recreate the file with the same name so it remains a single running document.
- If there are no new key messages since the cutoff, still add a
## YYYY-MM-DDsection noting "No notable updates today."
- Create or update a Gmail draft:
- Create a draft email to arnaud.lhote@zurich.ch (or update today's draft if one already exists from an earlier run today).
- Subject:
SPCt Slack Digest - YYYY-MM-DDusing today's date. - Body: a concise summary of today's key messages, each with its Slack permalink so the recipient can jump straight to the conversation. Mention that the full historical log is maintained in the Google Drive file
SPCt Slack Digest.md. - Do NOT send the email - only create or update the draft. The recipient will review and send it manually.
Be concise but informative - the goal is a quick, scannable daily briefing, with the full history preserved in the markdown log on Drive.
Connect and Authorize your Slack.
Claude Model
Sonnet (default)
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
Claude 1.12603.1 (3df4fd) 2026-06-11T16:57:36.000Z
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗