Slopgoataexperiment
Open Slopgoat

A working lunch bot in about five minutes.

Connect one workspace, invite Slopgoat to one lunch channel, and choose who belongs on the panel. No bot-building vocabulary required.

Install Slack AppSee what it can read

You’ll need permission to install apps in your Slack workspace.

Workspace → first thread
4 checks
  1. 1
    Approve in SlackChoose the workspace
  2. 2
    Invite to #lunchOne channel, explicitly chosen
  3. 3
    Select the panelChannel or Slack user group
  4. 4
    Review and startTest message is optional
Same installer, same workspace, one lunch channel.

Bring three things.

  • App permission from your Slack workspace
  • A lunch channel you can invite the bot into
  • Your team source: that channel, or an optional user group

Four checks. One functioning goat.

The setup wizard saves each choice to your workspace. Nothing depends on analytics, and nothing is sent to the panel until you approve the final review.

  1. 01

    Approve the Slack app

    Choose the right workspace and approve the requested permissions. Use the same Slack account for the next step so Slopgoat can confirm who installed it.

    Best handled by a workspace owner or someone allowed to install apps.
  2. 02

    Invite it to lunch

    In Slack, open the channel where lunch already happens and invite Slopgoat. Private channels work too—the bot just has to be a member.

    /invite @Slopgoat
  3. 03

    Choose the panel

    Pick the lunch channel or a Slack user group as your roster. You will preview the active humans before anyone is added; bots and deleted accounts stay out.

    A user group is optional. One channel is enough for most teams.
  4. 04

    Check the result, then go

    Confirm the timezone, review the member count, and decide whether to send a test post and intro DMs. Slopgoat will tell you exactly when the first lunch thread opens.

    You can change the channel, roster, retention window, or notification choices later.

What the bot can see—and what it cannot.

Slack shows the technical permission names. Here is what those permissions mean in actual lunch terms.

Reads
The lunch channel you choose, receipt files pasted there, and replies in its own DMs.
Writes
The daily lunch thread, a setup test if you request one, and private review prompts.
Matches
Active people from your selected channel or user group to panel members.
Doesn’t do
Scan the rest of the workspace, add bots as diners, or send Slack content to GA4.

Raw Slack message text is kept for 30 days by default. Admins can choose 7–90 days; message text and file metadata are cleared after that window.

Questions before you connect.

Put lunch under controlled observation.

The wizard will pick up exactly where this guide leaves off.

Install Slack AppBack to home