Integrations · Slack

Connect noombat to Slack

noombat posts the morning list and its alerts into the channels you choose, and answers questions where your team talks. One install from your noombat settings, about 5 minutes, no admin rights on the Slack side on most workspaces.

Direction

noombat posts into it

Access

The noombat Slack app, installed from your noombat settings through Slack's own consent screen

Time

About 5 minutes

Who

A noombat org admin; on workspaces that restrict app installs, a Slack admin approves it

Cost on your side

Nothing: the app uses no Slack seat

Before you start

What to have ready.

  • An org admin in noombat: connecting a workspace wires the whole team's channels into the org's data, so it is an admin act.
  • A channel for the list. Most teams create one called #signals in the workspace where the revenue team lives.
  • Some workspaces let only Slack admins approve new apps. If that is you, the install pauses at Slack's approval screen until an admin says yes.

What noombat posts

What lands in Slack.

The morning listthe companies worth contacting today, each with its reason, posted to the channel you choose, one message per account owner where you want that
Alertsan account turning hot, a meeting booked, a lead routed to someone, a scheduled routine finishing, a sync failing
Snout in a DMask the analyst about your own data; it answers with the numbers, a table or a chart
@noombat in a channelmention it in a thread and it answers there
/noombatthe slash command, for a quick question without leaving the channel
Files and canvasesa CSV or a report delivered into the channel, and a canvas that stays current

Setup

3 steps, about 5 minutes.

  1. 1Start the install from your noombat settings
  2. 2Approve the app in Slack
  3. 3Choose the channels
  1. 1

    Start the install from your noombat settings about 1 minute

    noombat > Settings > Integrations > Slack > Connect

    The install starts inside your noombat session, so the workspace is tied to your organisation before Slack ever sees the request. There is no install link to pass around.

  2. 2

    Approve the app in Slack about 2 minutes

    Slack shows what the app asks for. The list is the one below, and each item names the reason.

    chat:write, chat:write.publicpost the list and the alerts, in public channels too
    im:write, im:history, im:readopen a DM to deliver an alert, and read the questions you send Snout
    app_mentions:read, channels:history, groups:historyread a thread it is mentioned in, in public and private channels
    channels:read, groups:readchannel names, so you can pick one in noombat
    commandsthe /noombat command
    files:write, files:read, canvases:writedeliver a CSV or a report, and keep a canvas current
    users:read, users:read.emailmap a Slack account to a noombat member, so a DM answer goes to the right person
    reactions:writethe acknowledgement on a message it has picked up

    Click Allow. Slack sends you back to your noombat settings, where the workspace now shows as connected.

  3. 3

    Choose the channels about 2 minutes

    noombat > Settings > Integrations > Slack

    • Pick the channel for the morning list
    • Pick the channel for alerts, or keep both in one
    • For a private channel, invite @noombat to it first; Slack lets an app post in a private channel it is a member of

    We post a test message the same day and confirm back to you. From the next morning, the list arrives at the time you set.

Troubleshooting

What you might see, and the fix.

Every row is a failure we have met or verified. If yours is missing, send it over.

What you seeWhyFix
The Connect button says the install is forbiddenYour noombat role is a member, and connecting Slack is an admin act.Ask an org admin to run step 1.
Slack shows "This app needs approval" and stopsThe workspace lets only Slack admins approve new apps.A Slack admin approves the request under Slack's Manage apps > Requests; the install then continues.
The list arrives in the channel, and a DM to Snout gets no answerSlack could not map your Slack account to a noombat member, usually because the two use different email addresses.Sign in to noombat with the email on your Slack account, or ask an admin to invite that address.
Nothing posts in a private channelThe app is not a member of the channel.Invite @noombat to the channel; posting starts with the next message.
Every post stopped after a Slack admin changeThe app was removed from the workspace or its tokens revoked; Slack tells us the moment it happens.Run step 1 again; the reinstall takes two minutes.

Security and data

The questions a security review asks.

What can the app read?

A DM someone sends it, and a channel thread where someone mentions it. It has no scope to read the rest of a channel and no user token. The full scope list is in step 2, each with its reason.

Can several channels, or several workspaces, receive the list?

Yes. Each channel is a choice in your noombat settings, and each Slack workspace is its own install tied to one noombat organisation, so one customer's list can never land in another's channel.

What does this cost on the Slack side?

Nothing. The app uses no Slack seat and no paid Slack feature.

Does it work on Enterprise Grid?

Yes. The app is built for org-wide deployment from day one, so an install covers the workspaces your Slack admin allows.

How do we revoke it?

Remove the app from the workspace under Slack's Manage apps. Slack tells us the moment it happens, and every post and every answer stops. Reinstalling from noombat's settings brings it back.

Is our data safe with noombat?

Your data is kept apart from every other customer's, in a schema of its own, encrypted in transit and at rest, read through connections that write nothing back, and deleted when we part ways. Data-processing terms written for a security review, for teams in the EU and in the US. We walk through them with your security team on request.

Checked against Slack's own documentation. Last updated . Questions, or a policy in the way: integrations@noombat.ai