Remly Docs

Slack

Search messages and files live. Slack content is never indexed.

Status: Available – live search only · Last verified: 31 July 2026

Slack does not work the way the other connectors do. Search messages and files live. Slack content is never indexed. Remly queries Slack at request time and shows you what comes back, and nothing from Slack is written to Remly's document store.

This is deliberate, not a gap. Slack's API terms prohibit creating persistent copies, archives, or indexes of another organisation's API data.

What live search means for you

Indexed connectorsSlack
Content stored in RemlyYes, as derived chunks and embeddingsNo
Searchable semanticallyYesNo – Slack's own search does the matching
Can ground an Ask answerYesNo
Reachable over MCPYesNo
Results reflectLast syncRight now
Sync scheduleYesNot applicable – nothing syncs

So Slack results are always current, and Slack content never sits in Remly's index. The trade-off is that Slack does not participate in the parts of Remly that depend on indexed content: semantic matching, cited Ask answers, and MCP.

Personal scope

A Slack connection is personal to the account that authorises it. It searches with your Slack identity – you see what you can see in Slack, including your DMs and private channels you belong to – and it is not shared with anyone else.

Connecting

Open Connections, click Slack, and complete the Slack OAuth flow. Remly requests read scopes only. It never posts messages, reacts, or changes anything in Slack.

Credentials

The OAuth token is stored encrypted server-side. If it is revoked or expires, the card flips to an error state with a Reconnect action.

Disconnecting

Connections → Slack → Disconnect revokes the token with Slack and deletes the source row and credentials. Because Slack content is never indexed, there is no derived content to purge. Your account and every other connector are unaffected.

Plan requirement

Slack is a cloud connector and requires the Full tier. See Plans and billing.

On this page