Slack

Mention Proof with a customer task. It runs the scenario in a clean browser and returns the result and video evidence to the same Slack thread.

Ask Proof to check something

Mention the bot in a channel where it is installed. After the first mention, Proof subscribes to the thread, so follow-up messages in that thread can start additional tasks.

text

@Proof complete checkout with a declined card and confirm the order is not created

Write a good task

Name the customer goal, important condition, and observable outcome. Prefer “invite a viewer and confirm they cannot change billing” over “test permissions.” You do not need to list clicks or selectors—the browser agent chooses steps from the page it sees.

Include the edge case or account state.
State the business outcome that must or must not happen.
Avoid real customer credentials or secrets in the message.

What Proof posts back

Proof first acknowledges the task with a run link. When the durable workflow finishes, it posts the terminal status, report summary, the same run link, and expiring links to presentation video evidence when available.

Paused means no spend

If a cost interlock is off, the bot says whether live execution or AI is paused and does not start a browser or model run.

Administrator setup

The Slack app needs SLACK_BOT_TOKEN and SLACK_SIGNING_SECRET. This initial implementation maps Slack to one default organization, repository, and browser URL through PROOF_DEFAULT_ORGANIZATION_ID, PROOF_DEFAULT_REPOSITORY_ID, and PROOF_DEFAULT_BASE_URL.

Set the Slack event URL to https://your-proof-host/api/webhooks/slack and subscribe the app to mention events. The adapter verifies Slack signatures before processing a message.