slackActivity

Multi-user app that updates each connected user's Slack status with their currently playing Spotify track.

Setup

1. Copy .env.example to .env.
2. Create a Slack app and set the redirect URL to http://localhost:3000/auth/slack/callback.
3. Add Slack user scopes: users.profile:write and users.profile:read.
4. Create a Spotify app and set the redirect URI to http://localhost:3000/auth/spotify/callback.
5. Fill in SLACK_CLIENT_ID, SLACK_CLIENT_SECRET, SPOTIFY_CLIENT_ID, and SPOTIFY_CLIENT_SECRET.
6. Run npm start.
7. Open http://localhost:3000 and connect Slack, then Spotify.

Use npm run local for the old single-user local watcher.

Local Agent

The hosted app can read Spotify through the Spotify API, but Steam and desktop apps must be detected on the user's own computer.

Run the local agent on the user's computer:

$env:SERVER_URL="https://your-app-name.herokuapp.com"; npm run local-agent

The agent opens the hosted app in the browser. After the user authorizes Slack and Spotify, the agent saves its local token in ~/.slack-activity/agent.json and starts reporting Steam games and supported desktop apps. Fresh local activity takes priority over Spotify.

Heroku

Attach Heroku Postgres before connecting users:

heroku addons:create heroku-postgresql:essential-0 -a your-app-name

Heroku will set DATABASE_URL automatically. Without Postgres, connected users are stored in SQLite and will disappear after redeploys or dyno restarts.

Set these config vars to your Heroku app URL:

BASE_URL=https://your-app-name.herokuapp.com
SLACK_REDIRECT_URI=https://your-app-name.herokuapp.com/auth/slack/callback
SPOTIFY_REDIRECT_URI=https://your-app-name.herokuapp.com/auth/spotify/callback

Add the same callback URLs in the Slack and Spotify app dashboards.