Slack

Jev Events reads each new message in the channels your Slack app is in, asks Jev your questions about it, and runs what you pick on the answers. Choose below, and the code and the steps to run it fill in.

import { monitor, recipes } from "jev-events";import { slack } from "@jev-events/slack";const team = monitor({  // Also judges the 5 latest messages each time it starts, so there's something to see right away.  source: slack.messages({ backfill: 5 }),  questions: {    urgent: recipes.team.urgent,    needsAnswer: recipes.team.needsAnswer,  },  // Native actions only log what they would do. Set dryRun: false once the answers look right.  dryRun: true,})  .on("urgent", { min: 0.9 }, slack.post("#incidents"))  .on("needsAnswer", { min: 0.8 }, slack.react("eyes"));await team.start();console.log("Watching for new messages. Stop with Ctrl-C.");

Try it without codeCopy Anchor Link

To see what Jev says about your own workspace before writing anything, install the integration, set up the app once and watch. It prints an answer for the 5 latest messages, then for each new one:

npm i jev-events @jev-events/slack
npx jev-events auth slack
npx jev-events watch slack

watch slack:general reads one channel. By default it asks whether each message needs an answer, whether it's urgent, and what kind of message it is. Ask your own with --ask "bug=Is this reporting a bug?". See the CLI.

The first time, auth slack prints a link that creates the Slack app with everything filled in. Install it to your workspace, paste the two tokens it asks for, and invite the app to a channel with /invite @jev_events.

The sourceCopy Anchor Link

slack.messages() emits each new message in the channels, private channels and DMs the app is in.

Messages arrive in one of two ways, and the builder sets up the right one:

A web app can also use Socket Mode for every workspace that added your app, over one connection: pass slack.app({ appToken }) or set SLACK_APP_TOKEN, and run jev.start() in a process that stays up.

ActionsCopy Anchor Link

text can be a string or a function of the event, such as (e) => `<@${e.item.author.id}> on it` , and Slack formatting such as *bold* works. When the app isn't in a channel or lacks a scope, the error says what to type or click to fix it. Actions are dry-run until you pass dryRun: false to monitor().

MessagesCopy Anchor Link

Handlers receive a SlackMessageItem:

Jev sees the text and the author's name, plus facts: the channel, and whether it's in a thread, mentions the app or everyone, or comes from a guest, a bot or another company.

Good to knowCopy Anchor Link

• Skipped before judging. Joins, edits, the app's own posts and other bots are never judged, so they cost nothing.
• Slack wants an answer within 3 seconds. In a web app, the runtime answers Slack first and judges the message after, through waitUntil: after from next/server. Keep the route's maxDuration long enough to judge.
• Retries. A message that fails for a reason that may pass, such as Slack being down, answers an error so Slack sends it again: 3 times over about 5 minutes. A workspace that removed the app answers OK and is marked needs-sign-in.
• Keep token rotation off in your app's settings. The saved bot token has to keep working.
• A server with one workspace of your own. slack.fromEnv() builds the connection from SLACK_BOT_TOKEN and SLACK_APP_TOKEN: await team.start({ connections: [slack.fromEnv()] }).
• Your own manifest. manifestUrl({ name, requestUrl, redirectUrls }) makes the link that creates the app with everything filled in, and manifest() gives it as an object.