Connect Harvv to Slack

Four steps. Then one command that tells you whether it actually worked.

Steps verified against the live Slack and Harvv screens, August 2026.

Start in Harvv, not in Slack. Harvv is not in the Slack app directory, so searching Slack for it will not find anything.
  1. 1

    Connect from Harvv

    Not from Slack. Searching Slack for Harvv will not find it.

    In Harvv go to Settings, open the Integrations tab, and click Connect on the Slack card.

    Settings SITE PROFILE GENERAL INTEGRATIONS S Slack Ask questions and get findings in a channel Connect
  2. 2

    Approve it in Slack

    Slack asks which workspace, then shows what Harvv can do.

    Pick your workspace and click Allow. You land back in Harvv and the card says the bot is installed.

    Slack Allow "Harvv" to access Slack Workspace Your workspace WHAT HARVV CAN DO Allow
  3. 3

    Pick a site and a channel

    This one happens in Slack, and it is the step people skip.

    In any Slack channel type /harvv setup. Harvv messages you back. Choose the site to answer about, and the channel new findings should post to.

    Harvv Harvv is connected. Two quick choices. Which site should I answer about? Your site v Where should I post new findings? Pick a channel v Save
  4. 4

    Ask it something

    Three places work. Slackbot is not one of them.

    Open Harvv in your sidebar and use the Messages tab, or type @Harvv in a channel, or /harvv your question anywhere.

    Slack Slackbot Channels AGENTS & APPS Harvv Home Messages Message Harvv or @Harvv in a channel, or /harvv anywhere Slackbot cannot reach Harvv

Check that it worked

In any Slack channel, type:

/harvv check

Harvv tests the connection, the bot token, the permissions Slack actually granted, whether a site and a channel are chosen, and whether Slack is really delivering messages to Harvv. Every line that is not a green tick tells you what to do about it. Anything Harvv cannot verify is reported as unverified rather than passed. Only you see the result.

Using the Harvv MCP connector instead? Ask it to check the Slack integration. It runs the same test.

The one thing that trips people up

Slack has its own assistant called Slackbot. It is a separate app. Anything you type to Slackbot never reaches Harvv, and Harvv cannot see it or reply to it. If the bot seems to be ignoring you, check which app you are typing to.

Questions

I searched Slack for Harvv and found nothing. Where is it?

Harvv is not in the Slack app directory, so searching Slack will never find it. You start in Harvv: Settings, then the Integrations tab, then Connect on the Slack card. That is what puts the app in your workspace.

I asked Slackbot and it did not know anything about my site.

Slackbot is Slack's own assistant and a completely separate app. It cannot pass anything to Harvv, and Harvv never sees what you type to it. Message the Harvv app directly, mention @Harvv in a channel, or use /harvv instead.

The bot answers me but never posts anything on its own.

That means no channel was picked. Answering questions and posting new findings are set up separately. Type /harvv setup in Slack and choose a channel. If you only want to ask questions, leaving it empty is a valid choice.

How do I know it is actually working?

Type /harvv check in Slack. It tests the connection, the bot token, the permissions Slack actually granted, whether a site and a channel are chosen, and whether Slack is really delivering messages to Harvv. Anything it cannot verify is reported as unverified rather than passed. Only you see the result.

Who in my workspace can use it?

Anyone in the Slack workspace can ask the bot questions. Answers cover the sites on the Harvv account that connected it, and questions run against that account's credit balance.

How do I disconnect it?

In Harvv: Settings, then the Integrations tab, then Disconnect on the Slack card. The stored bot token is erased immediately, so Harvv can no longer post or read in your workspace. Nothing is deleted from your Harvv account and you can reconnect later.