Slack: channel history and custom skills
What the Slack integration does out of the box, when you need a custom skill to read or summarize channel history, and what to check when a Slack connector doesn't fire.
Adding your clone to Slack lets people message it like a colleague. Reading back through a channel's history, for example to summarize last week's discussion, is a different job. It needs a custom skill.
What works out of the box
With the Slack integration, your clone joins your Slack workspace as its own Slack app. Invite it to a channel and it responds to messages there: @mention it or message it, and it replies with the same knowledge and skills it has in Clone Studio.
To set it up, open Integrations → + Add Chat Platform, choose Slack, and follow the numbered steps. See Reach your clone anywhere.
What needs a custom skill
Responding to a message is not the same as reading the channel. These jobs need a custom skill:
- Scraping a channel's message history
- Summarizing a channel or thread over a time window ("what did #engineering decide this week?")
- Pulling decisions, action items or questions out of past messages
- A daily or weekly digest of one or more channels
Once the skill exists, you can run it from chat or put it on a schedule. See Put your clone on a schedule.
How to get a custom Slack skill
Option 1: Request one
Ask your clone to open a support case, or open one here, and mark it as a Skill Request. Include:
- Which channels (names, public or private)
- What to read: the time window, and whether to include threads
- What you want back: a summary, a list of decisions, action items, a digest
- Where it goes: a chat reply, an email, a post in another channel
- How often: on demand, daily or weekly
- Which clone should have the skill
See How to open a support case.
Option 2: Build it in Skill Forge
If your team builds its own skills, create one in Skill Forge. Describe the same six things above, test it on one channel first, then turn it on for the clone that needs it.
Troubleshooting: when a Slack connector doesn't fire
Work through these in order.
- Skill enabled on the clone. Load the clone with the clone chip, open Skills, and check the Slack skill is listed and Enabled. Skills are per clone.
- Connection bound. The skill should show at least one connection. If it shows 0, bind the Slack connection to the skill, or reconnect it.
- Clone invited to the channel. The clone's Slack app must be a member of the channel. In Slack, invite it to the channel (for example, type
/invite @YourCloneName). Private channels always need an invite. - Per-skill enable override. A skill can be on in general but switched off by an override for this clone. Check the skill's own enable setting and make sure nothing overrides it to off.
- Integrations power switch. On the Integrations page, make sure the power switch is on. Off pauses the clone on every channel.
- Execution Log. Send a test message, then open the Execution Log. If the skill never ran, ask more directly ("Use the Slack skill to summarize #general for today"). If it ran and failed, the error usually says why.
Still not working? Open a case with the clone, the skill, the channel, what you asked, and a screenshot of the Execution Log. See When a skill isn't working.
Common questions
My clone answers in Slack but can't tell me what was said yesterday. Is it broken? No. Out of the box it responds to messages. Reading channel history needs a custom skill.
Can I get a weekly digest of a channel? Yes, with a custom history skill and a schedule.
Does it work in private channels? Only channels the clone's Slack app has been invited to.
Who approves the Slack app? Your Slack workspace admin may need to approve it when you add the integration.
Related
Was this helpful?
Thanks. That helps us make this better.