Source: https://docs.pageloop.ai/guides/slack-integration

# Slack integration

# Slack integration

Connect Slack to find documentation gaps in product and support discussions, request documentation work in a conversation, and receive run updates and questions where your team works.

Slack is a source of evidence and a place to collaborate. It is not your documentation publishing destination. [Connect a knowledge base](/guides/connect-knowledge-base) so Pageloop can compare conversations with your articles and prepare changes for review.

## Before you begin

- Sign in to Pageloop as an **Admin** to connect or configure Slack. Editors and Contributors can view integrations but cannot change their configuration.
- Use a Slack account allowed to authorize the app in the workspace you want to connect. Follow your workspace's app-approval requirements.
- Choose one to three channels containing relevant product, release, or support discussions, one notification channel, and one or two people to tag.
- Invite the Pageloop app to any private channel you want to use before selecting that channel in Pageloop.

> [!NOTE]
>
> The notification channel can receive questions containing context from documentation work. Choose its membership with that visibility in mind and review [who can use Ask from Slack](/guides/ask-pageloop#ask-from-slack), including people without a Pageloop account.

## Connect and configure Slack

1. Open **Integrations** from the sidebar, or **Settings → Integrations**.

2. Find **Slack** under **Messaging** and select **Connect**. You can use **Search integrations** to find the card.

   ![Slack card under Messaging with Connect outlined](/images/uploads/uploaded-image-0-57136233.png)

3. Review Slack's requested permissions and approve the app for the intended workspace.

4. Back in Pageloop, **Connecting Integration** appears, followed by the **Integration connected** toast. **Configure Slack Channels Access** opens with “Choose channels from your connected workspace.” Complete all three fields:

   - **Select channels Pageloop should watch for updates (1-3 required):** select the channels for proactive documentation checks.
   - **Select the channel Pageloop should notify when updates are ready (1 required):** select the destination for Pageloop's questions, not run results.
   - **Select the users we should tag on the notification (1-2 required):** select the people to mention when Pageloop cannot match the person who asked.

   ![Configure Slack Channels Access with watched channels, a notification channel, people to tag, and Save Configuration outlined](/images/uploads/uploaded-image-1-c156f551.png)

   ![Watched channels picker with search and channel checkboxes](/images/uploads/uploaded-image-2-be60e2db.png)

5. Select **Save Configuration**, which is enabled once all three fields are filled. Pageloop attempts to join the chosen public channels, including the notification channel. For a private channel, add the Pageloop app to it in Slack first.

6. Check for **Configuration saved**. Reopen Slack's gear button (**Configure**) to confirm the saved channels and people.

![Integrations filtered to Slack, with its Connect button under Messaging](/images/uploads/screenshot-02b8b0cb.png)

The card shows **Connected** and the **Configure** gear immediately after connecting, even before you save channels. Nothing is watched or posted until you save the configuration. You can revisit the configuration to change channels or notification recipients. A **Connected** card does not mean a workflow is active or that every discussion will produce a suggestion.

## Permissions and what Pageloop can read

Slack authorization requests bot permissions to read and post in public and private channels the app is in, read direct messages with the app, list channels and people, look up people by email, join public channels, and add reactions. It also requests user permissions for search, files, and people. Review the full permission list in Slack before approving it; the requested permissions are broader than any one documentation workflow.

| Access path       | What it reads                                                                                                                              | Boundary                                                                                                                      |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
| Channel discovery | Channel names, IDs, private/public status, app membership, and whether a channel is tracked.                                               | Private channels are visible to the app only where Slack permits access.                                                      |
| Channel history   | Top-level messages, authors, timestamps, reply counts, and message links for a chosen time window.                                         | The app must be a member of the channel, public or private. Research runs do not join channels automatically.                 |
| Thread reads      | The conversation and replies behind a supplied or discovered Slack message link, including message text and available attachment metadata. | The link must come from the request or an authorized source result, and the app must be able to access the conversation.      |
| Search            | Relevant messages in public channels using the connected user's search authorization.                                                      | Search is not limited to the watched channels. Private-channel and direct-message search are not enabled by this search path. |
| People lookup     | Member names and profile information used for author names, notification recipients, and mentions.                                         | Subject to the permissions approved in Slack.                                                                                 |

> [!WARNING]
>
> Watched channels define the intended scope of scheduled checks, not a workspace-wide search permission boundary. Pageloop's workflow guidance tells the agent to ignore search results outside the tracked channels. Channel-history reads can also reach other channels the app belongs to when the task calls for them.

For a private discussion, invite the app to the channel and provide the thread link in your request. Do not assume a public-channel search can discover that private thread.

## Supported workflows

### Find documentation gaps on a schedule

For Pageloop-hosted knowledge bases, saving the configuration with at least one watched channel creates a draft workflow named **Keep docs in sync with Slack**, scheduled daily at **09:00** in your time zone. Open **Workflows** to activate or edit it. Tell the workflow what to look for, the relevant channels, and the desired documentation result. See [Create and manage workflows](/guides/workflows) for testing, activation, and scheduling.

Scheduled checks start only when watched channels have real messages since the last run. Channel joins, topic changes, and Pageloop's own posts do not count. Otherwise, the check reports **Nothing new since the last run**. If Pageloop was removed from every watched channel, runs fail with **Slack is disconnected**.

Pageloop reads the tracked channels for the run's time window, follows relevant threads, and compares confirmed explanations with your documentation. Each run can make up to 30 Slack calls. Repeated questions, corrections, and answers can reveal missing or inaccurate instructions. An unanswered question, an unconfirmed remark, or a discussion already covered by your docs does not necessarily produce an edit.

The run proposes changes in the **Inbox** for a person to review. Connecting Slack or activating a check does not publish documentation.

### Ask or request documentation work in Slack

Use a Slack conversation to ask about your documentation or request a documentation change with the thread as context. For how to address Pageloop, follow-up behavior, and when a run starts automatically or waits for **Start**, see [Ask from Slack](/guides/ask-pageloop#ask-from-slack).

Full members of the connected Slack workspace can ask Pageloop. Guests and people from other workspaces receive “Sorry, I can only help people in this Slack workspace.” Messages can contain up to 4,000 characters. The limits are 20 questions per person per hour and 300 per workspace per day. At the limit, Slack shows “You've reached the limit for asking Pageloop right now. Try again later.”

### Receive questions and answer them

The notification channel receives questions from runs started outside Slack and unanswered Pageloop chat questions after about 10 minutes, not run results. Pageloop tags the person who asked when it can match them; otherwise, it tags the people you chose in the configuration. Runs started in Slack use their conversation thread for updates.

See [Answer the agent's run questions](/guides/ask-pageloop#answer-the-agents-run-questions) for the answer form and [Answer a question from a Pageloop chat](/guides/ask-pageloop#answer-a-question-from-a-pageloop-chat) for delivery timing and how answers continue the original chat.

### Post a workflow summary

A live workflow can post a summary to an allowed Slack channel named in its steps. Use a channel mention to identify the destination and explicitly ask for a post. A test run does not send Slack posts; it includes the proposed message in its summary instead. See [Workflow mentions](/guides/workflows#use-mentions-in-steps).

## Disconnect Slack

1. Point at **Connected** on the Slack card; it changes to **Disconnect**. Select it.
2. Review **Disconnect Slack?**.
3. Select **Disconnect** to confirm, or **Keep connected** to cancel.

![Disconnect Slack? dialog with Disconnect outlined and Keep connected available](/images/uploads/uploaded-image-4-3a9a9a66.png)

The **Slack disconnected** toast confirms the change. The Pageloop app leaves every channel, and both Slack tokens are revoked. Slack questions and posts stop. The draft workflow stays in **Workflows**, but its runs fail with **Slack is disconnected**.

## Reconnect Slack

Admins see **Needs reconnecting** on the card when Slack access needs repair, with “Slack needs to be reconnected. Pageloop lost access, so it is paused until you reconnect it.” This can happen when the Slack token was revoked, the search authorization is missing, or the app was installed before a permission Pageloop needs was added.

Select **Reconnect Slack** and approve all requested permissions. Your saved channels are kept.

## Limitations and troubleshooting

| Symptom                                                                                                                          | What to check                                                                                                                                                                             |
| -------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Save Configuration** is disabled.                                                                                              | Select one to three watched channels, one notification channel, and one or two users. Wait for channel and member lists to finish loading.                                                |
| A private channel is missing, or “Invite the Pageloop app to these private channels in Slack, then save again: `<channel IDs>`”. | Invite the Pageloop app to the private channels in Slack, reopen the configuration, and save again. The dialog remains open after a failed save so you can correct the selection.         |
| “Failed to join the following channels: `<channel IDs>`”                                                                         | Slack refused the join because of permissions, workspace policy, or an archived channel. Check the affected channels and app access before saving again.                                  |
| “Failed to authenticate with Slack”                                                                                              | Reconnect Slack.                                                                                                                                                                          |
| Channel or people lists show “No channels available” or “No users available”.                                                    | The list did not load. Reopen the dialog later, or reconnect Slack.                                                                                                                       |
| “Could not connect” with “Failed to generate Slack installation URL”                                                             | Try connecting again.                                                                                                                                                                     |
| A saved channel shows **(Unavailable)**.                                                                                         | The channel may be archived, private, or absent from the loaded directory. Verify the channel and app membership; remove an obsolete selection if needed.                                 |
| Search is unavailable but a thread link still works.                                                                             | Public search needs a user search authorization, separately from the bot's thread access. Ask an Admin to use **Reconnect Slack** if offered and approve the requested Slack permissions. |
| A channel read is refused.                                                                                                       | Check app membership. A channel appearing in the directory does not prove the app can read its history.                                                                                   |
| A run reports partial Slack results or rate limits.                                                                              | Slack limits history reads, and runs have a shared Slack-call budget. Narrow the channels, time window, or topic rather than assuming an incomplete result covers all messages.           |
| There are no suggestions.                                                                                                        | Verify saved watched channels and an active workflow. Check the run history for no-change, skipped, or failed results; not every conversation reveals a documentation gap.                |
| Ask does not answer or questions do not arrive.                                                                                  | Check the notification channel and connection health; see [If Slack does not answer](/guides/ask-pageloop#if-slack-does-not-answer).                                                      |
| “This Slack workspace is connected to more than one Pageloop organization.”                                                      | A Slack workspace can serve only one Pageloop workspace. Use a Slack workspace connected to just one Pageloop workspace.                                                                  |

## Related guides

- [GitHub integration](/guides/github-integration)
- [Jira integration](/guides/jira-integration)
- [Linear integration](/guides/linear-integration)
- [Where Inbox items come from](/guides/where-inbox-items-come-from)
- [Review an Inbox item](/guides/review-inbox-item)
