Docs/Slack
#

Slack

Connect Slack to receive alerts about automation results and test failures directly in your workspace.

Connect Slack to get real-time alerts when automation rules complete or fail, and to build, run, and troubleshoot workflows in a conversation — without leaving Slack.

Once connected, you can:

  • Get alerts in channels — workflow test suites, QA runs, and crawls, routed per rule.
  • Get personal alerts — direct messages tied to your linked account.
  • Work with the assistant in a thread — ask questions, search Jira and Linear tickets, and follow live progress.
  • Build and run from Slack — create, revise, re-run, and troubleshoot workflows, and launch ad-hoc tests.
  • Share results back — write ad-hoc verdicts and replays to linked Jira tickets.

01Prerequisites

  • A Slack workspace where you can install apps
  • Admin role in your Cofactor organization

02Connect Slack

  1. Go to Settings > Slack under Integrations.
  2. Click Add to Slack and authorize Cofactor for your workspace.
  3. Back in Cofactor, choose a Notification Channel and click Send Test Message to verify delivery.
  4. Review Account Linking and choose whether users must link their Cofactor account before write actions.
  5. Confirm the workspace shows a green Connected badge.

If the channel isn't listed, invite the bot first with /invite @Cofactor. Only admins can connect or disconnect Slack.

Settings → Slack — Add to Slack connects your workspace

Tip: A dedicated channel like #cofactor-alerts keeps notifications out of team conversations.

03Send notifications to a channel

Slack alerts come from notification rules. Add a Slack step to any rule:

  1. In the rule's Alerts section, click Add Alert Step.
  2. Set Channel to Slack and pick the channel.
  3. Choose when to send: success, failure, or both.
  4. Click Join & Send Test to verify delivery.

A rule can have multiple alert steps, so you can fan out to different channels or mix Slack with email. Alerts include the rule name, success/failure, a result summary, and error details for failures.

For personal notifications, link your account under Settings > Notifications and choose Slack as your delivery method.

04Work with the Slack assistant

Start a thread where the Cofactor app is available, ask a question, and keep the conversation in that thread so Cofactor can track context and post progress. You can:

  • Search tickets — ask about a Jira or Linear issue, or paste a key or link, to pull the latest details into the thread.
  • Build and troubleshoot — ask Cofactor to create or revise a workflow, re-run the latest version, explain a failure, or run an ad-hoc test for what you're discussing.

Cofactor posts in-progress updates and completion status — success confirmations and failure diagnostics — in the same thread. Keep one thread per workflow or ticket to make updates easy to follow; open the run or workflow in Cofactor when you need deeper inspection.

If your workspace uses account linking, complete the link flow the first time Cofactor asks. Linking attributes Slack-triggered tests and workflow actions to you instead of a shared admin identity.

A Slack thread — ask the assistant to test something, get the verdict and replays back in-thread

05Run tests from Slack

Run ad-hoc tests to validate a fix, reproduce an issue, or verify a result in the conversation:

  1. In a thread where the Cofactor app is available, ask Cofactor to run the workflow or test the scenario.
  2. Complete account linking if prompted.
  3. Confirm the execution target if Cofactor offers a sandbox choice.
  4. Follow the in-progress updates and final status in the thread; open the linked run in Cofactor for deeper investigation.

If your property has a default sandbox, Slack-launched tests use it automatically; otherwise they run against the property's live URL unless you pick another target.

Sharing results back to Jira. When the thread references a Jira ticket, Cofactor writes the result back after the run — a comment with the verdict and summary, verified issue details, and links to the run and replay artifacts. Slack keeps the live progress; Jira keeps the issue record. See Jira for the full write-back.

06Test the connection

  1. Go to Settings > Notifications.
  2. Choose the Slack destination you want to verify.
  3. Click Send Test and check the channel or your DMs.

If it doesn't arrive, confirm Slack is still connected, the bot is in the channel, and your account is linked (for personal notifications).

07Disconnect Slack

Go to Settings > Slack, click Disconnect, and confirm. Automation rules with Slack alerts stop sending until you reconnect.

08Permissions

ActionRequired role
Connect or disconnect SlackAdmin
Configure automation alerts and channelsAdmin
Send test notifications to channelsAdmin
Choose Slack as a personal destination / send a personal testLinked user account
Build, run, and troubleshoot workflows from SlackMember with access to the Cofactor app