Slack
Connect your Repave server to your Slack workspace, and two things work there:
- Agent questions come to you. When an agent stops to ask a question, Repave posts it in Slack, and your answer there answers the run, exactly as if you had answered in Repave.
- You can ask Repave. Mention @Repave in a channel, or send it a direct message, to ask about a project ("Why did Login fail?") or to ask for a change ("Reword the Login error message").
Connect Slack (administrators)
Your Repave server connects its own Slack app, made from a manifest the server writes for you. Nothing goes through a service run by Repave: messages pass between your server and your Slack workspace only.
- Open Admin portal → Slack and choose Copy manifest.
- In Slack, open api.slack.com/apps, choose Create New App → From a manifest, pick your workspace and paste the manifest. If your workspace needs apps approved, a Slack admin approves it.
- Install the app to your workspace. Copy its Bot User OAuth Token (OAuth & Permissions,
starts with
xoxb-) and create an App-Level Token with theconnections:writescope (Basic Information, starts withxapp-). - Paste both tokens into Admin portal → Slack and choose Save. Repave checks both with Slack before it keeps them, and shows Connected to your workspace.
Make one Slack app for each Repave server. Two servers that share an app split its messages between them, so a UAT and a production server each need their own. The manifest names the app after your server, so they are easy to tell apart.
Network
The connection is outbound only: your server opens a connection to Slack, and Slack never calls
in, so the server needs no public address. Allow outbound HTTPS to slack.com and *.slack.com.
If your server reaches the internet through a proxy, Repave uses the deployment's HTTP_PROXY,
HTTPS_PROXY and NO_PROXY. A proxy that inspects TLS needs its certificate authority trusted
through NODE_EXTRA_CA_CERTS, as for any other outbound call.
A server without internet access cannot reach Slack. Save then shows the network's error, and nothing else changes.
Who is who
Someone in Slack acts as the Repave account with the same email address. When their Slack email matches no account, Repave offers them Connect your Repave account: a link, valid for 15 minutes, that connects their Slack account to whichever account signs in to open it. Because emails decide who is who, connecting Slack trusts your Slack workspace's admins, who set them.
Everyone has the same access in Slack as in Repave: only a project's editors can answer its questions, and Repave answers questions only about projects the asker can see.
Where agent questions go
Each project chooses in Settings → Integrations → Slack:
- Direct messages (the default): to the person who started the run and the feature's owner, the same people a desktop notification reaches. Repave finds them in Slack by their email.
- Channel: once, to the channel you pick. Repave joins a public channel when you save. Invite @Repave to a private channel first. One channel serves one project.
- Both, or Off.
If Slack refuses a post, for example because the channel was archived, the card shows the error until a post works again.
On a run that autopilot is driving, Repave posts a question only once autopilot passes it to a person.
Answering in Slack
- A question with a few choices shows each as a button: choose one to answer.
- Answer… opens a form for anything else: several questions, more than one choice, or your own words.
- Replying in the question's thread answers it in your own words, when it holds one question. In a channel, mention @Repave in the reply.
- Every copy of the question then shows who answered and what. An answer given in Repave, or a run that ends first, shows there too.
Asking someone to help
Tag someone… on a question opens a form: pick another editor of the project and add a note if you like. You can also tag from the question's card in Repave. The person you tag hears about it where the project sends questions:
- Direct messages or Both: a direct message with your note and the question, or a reply under the question if they already have it.
- Channel: a reply in the question's thread that mentions them.
- Off: nothing in Slack; they still get the notification in Repave.
Only editors can tag, and only editors can be tagged.
Scenario changes and requests for permission to run a command are answered in Repave: Slack links to them with Open in Repave.
Asking Repave
Mention @Repave in a channel, or send it a direct message.
- Which project: in a project's own channel, that project. Otherwise your only project, or Repave asks which one you mean.
- Question or change: Repave works this out, and asks Just answer or Make the change when it is unsure.
- A question is answered read-only, from what you can see in Repave: status, specs, activity and costs. Repave posts "Looking into it…" and replaces it with the answer. Reply in the thread to follow up, and mention @Repave again in a channel thread.
- A change goes to the project's assistant, which a project owner turns on in Settings → Agents. It runs as you, and needs you to be an editor. Each of its replies is posted in the thread; its questions come there too.
Answers stay where the project put them: in the project's own channel Repave replies in the thread, and asked anywhere else it replies in your direct messages.