Skip to page content
Proof Docs

Slack

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

This reference describes the earlier Job workflow. It does not start website mapping or operate on mapping tests. Use the dashboard for that workflow.

Ask Proof to check something

Mention the bot in a channel where it is installed. After the first mention, follow-up messages in that thread can start more Jobs.

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 visible outcome. Prefer “invite a viewer and confirm they cannot change billing” to “test permissions.” You do not need to list clicks or selectors. Proof 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

If the request needs clarification, Proof posts questions and a Job link without starting browser work. For a runnable request, it posts a Job link and starts the test. When the Job ends, it posts the final status, a Finding summary when needed, and links to video evidence when available.

Administrator setup

The Slack app needs SLACK_BOT_TOKEN and SLACK_SIGNING_SECRET. Slack uses one default organization and Project. Configure them with PROOF_DEFAULT_ORGANIZATION_ID, PROOF_DEFAULT_REPOSITORY_ID, and PROOF_DEFAULT_BASE_URL.

The default Project needs current approved context and saved target settings from the earlier workflow. Mapping does not create those context approvals. The adapter uses PROOF_DEFAULT_BASE_URL to build the Slack request. Execution uses the Project’s saved test URL and network allowlist.

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.