Skip to main content
The Slack integration connects a team’s Slack workspace to xysq so that messages in the channels you choose flow into the team vault. Once connected, channel conversations become recallable memory the whole team shares, across every agent each member uses.
Slack is a team integration, not a personal one. Open it from a team at app.xysq.ai: go to your team and open the Apps tab (/teams/:teamId/apps).

​
Who can connect it

Connecting, choosing channels, and disconnecting are admin and owner actions. Any team member can see the connection status and recall what’s been synced, but only admins and owners manage the connection.

​
Connect Slack

  1. Open your team’s Apps tab and find the Slack card.
  2. Click Connect. A new tab opens for Slack’s OAuth consent screen. Sign in and approve access.
  3. The card flips from Pending to Connected.
The card shows the connection status at a glance:
StatusMeaning
Not connectedNo Slack connection for this team yet.
PendingOAuth started, waiting for consent.
ConnectedLive and watching your selected channels.
Paused (quota)The team’s daily event cap is reached; syncing resumes after reset.
ErrorSomething went wrong; reconnect to fix it.
DisconnectedThe connection was revoked.

​
Choose which channels to watch

Once connected, the card lists the channels the connected account can see. Toggle on the ones this team should watch. Private channels show a lock so you can tell them apart. Only messages in the watched channels are synced; everything else is ignored. You can change the watched set at any time. Adding a channel starts syncing its new messages; removing one stops it.

​
What gets synced

Messages in a watched channel are folded into the team vault as they happen. xysq captures human messages only, so bot and app posts (CI alerts, reminders, integrations) are skipped to keep the noise out. A message is stored with the author’s name, for example: 
[Ada Lovelace] so what do you think? is this feature cool or what?
Replies in a thread fold together with their parent under one document, so a conversation stays grouped rather than scattered into separate memories. Each memory is tagged so you can find it later: source:slack, slack:message, channel:<id>, and slack:thread_reply on replies. The author’s email (when Slack shares it) and the source channel, timestamp, and workspace are kept on the memory for provenance. Ask any connected agent, or xysq Chat, things like: 
What did the team say about the launch in #general this week?

Summarise the discussion on the new pricing in Slack.

​
Activity logs

Every Slack event xysq processes lands in the team’s activity logs. Open a team’s Logs tab (/teams/:teamId/logs) and switch to Apps to see what was kept, when, and from which channel.

​
Disconnect

Click Disconnect on the Slack card (admin or owner only). New messages stop syncing. Memory already in the team vault stays and remains recallable. Reconnect later to pick up new messages again.