DocumentationIntegrations
7 min readUpdated 16 August 2026

Slack

Connect Slack, choose where updates go, understand every notification, and work with requests without losing the source of truth.

Inside PIWOT℗
PIWOT℗ connections settings for installing Slack and choosing a channel

Connect the workspace first, then choose the channel that should receive request activity.

Inside PIWOT℗
PIWOT℗ notification settings with delivery controls for in-app, email, and Slack updates

The Slack connection chooses where updates can go. Notification preferences choose which supported events reach your account.

Where this fits

01

Connect

02

Choose

03

Notify

04

Review

01

Connect the correct Slack workspace

A PIWOT℗ workspace Admin connects Slack from Settings, then Connections. The authorization screen shows the Slack workspace and permissions being approved. One Slack workspace can be linked to one PIWOT℗ organization at a time, which prevents one team's channels from exposing another team's board.

  1. 01Open Settings, then Connections.
  2. 02Select Connect Slack workspace and confirm that Slack is showing the intended company workspace.
  3. 03Approve the requested access. PIWOT℗ returns you to Connections after Slack finishes authorization.
  4. 04Confirm the connected workspace name before choosing any notification channels.
02

Choose up to five notification channels

Select a channel, then use Save channel + test. PIWOT℗ saves the channel and posts a test message so you know the app can write there. You can add up to five channels, and enabled workspace notifications are posted to every channel in the list.

PIWOT℗ joins a public channel when you save it. For a private channel, the connection tries to invite the app for you. If Slack blocks that step, open the private channel's message box, run /invite @PIWOT, then return to PIWOT℗ and send the test again. Slack apps do not appear in the normal Add people search.

03

Customer notifications you can receive in Slack

The exact set depends on your workspace role and your controls in Settings, then Notifications. Slack carries day-to-day request activity. Billing, security, direct mentions, team changes, and other events can use different default channels, so do not assume every in-app or email notification will also be posted to Slack.

  • Needs your input: a request moved to Needs Input and is waiting on your team
  • Work started: a request moved to Active and design is underway
  • Request finished: a request moved to Done and is ready to review
  • New files: someone uploaded a file to a request
  • New comments: activity was added to a request discussion
  • Support replies: PIWOT℗ Support answered your conversation
  • Brand kit reminders: important brand context is still missing
04

Read a PIWOT℗ notification card

Request cards are live. When a supported status move succeeds, PIWOT℗ updates the existing Slack card rather than leaving a misleading old status behind. A short progress note appears in the card thread so the change is still visible in the conversation history.

  • Header: what changed and which request needs attention
  • Linked request title: opens the exact request in PIWOT℗
  • Workspace and actor context: shows where the update came from
  • Comment or file excerpt: includes the useful part of the update when available
  • Primary action: opens the request, delivery, file, support reply, or relevant settings area
  • Status actions: move the request when that action is available for its current state
05

What happens when you paste a PIWOT℗ request link

A link such as app.piwot.co/request/request-id opens that exact request after the viewer signs in. When the connected Slack workspace is allowed to view the request, PIWOT℗ can expand the pasted link into a request summary with its title, status, and useful actions.

The preview does not bypass PIWOT℗ access control. Someone who is not a member of the connected workspace still cannot use the link to open private request data.

06

Move requests from Slack

A request card can offer moves such as Move to Active, Move to Done, Needs input, or Return to Active. You can also react to a mapped request card with ⚡ for Active, ✅ for Done, or ✋ for Needs Input. The first supported reaction performs the move and refreshes the card.

Slack follows the same rules as the board. Moving into Active can fail when every Active lane is already in use. PIWOT℗ then explains which work is occupying capacity so you can finish or move another request before trying again.

07

Create, find, and review work without leaving Slack

The composer shortcuts beside Slack's message field also provide New request and Move a request. New customer requests begin in Backlog. Open the PIWOT app inside Slack and use its Home tab for a board snapshot, Active capacity, Needs Input, Backlog, Done, and the next useful action.

  • /new [title] or /piwot new [title]: create a request, with a form when more information is needed
  • /piwot status: show board counts, Active work, and requests waiting on input only to you
  • /piwot digest: post the same board picture visibly in the channel
  • /piwot list [backlog|active|needs|done]: list requests, optionally for one column
  • /piwot find <query>: search request titles
  • /piwot brief <query>: show the brief and latest comment
  • /piwot move: choose a request and destination in a form
  • /piwot done <query>: mark one unambiguous request Done
  • /piwot comment: choose a request and add a comment through a form
08

Know what a Slack thread does and does not sync

Plain replies under a request card stay in Slack. This gives your team room for internal conversation without automatically copying every message into the customer-visible request history.

Mention @PIWOT in a reply when the message should become a request comment. For an earlier reply, open the message menu and choose Add to request. To add a Slack file as a request note, share it in the request thread with @PIWOT. PIWOT℗ confirms in the thread when the comment or file note was added.

09

Link your Slack identity to PIWOT℗

PIWOT℗ first tries to recognize a Slack user from the available account information. If Slack and PIWOT℗ use different email addresses, type /piwot link. Slack returns a private link that works for 15 minutes. Open it while signed in to the correct PIWOT℗ account.

After linking, comments and status moves carry your PIWOT℗ name. Without a match, activity can appear as Someone via Slack. Use /piwot unlink to remove the explicit pairing. This identity link is different from a request link pasted into a channel.

10

Reconnect, test, or disconnect

Reconnect when private channels are missing, Slack says new permissions are required, or an older installation cannot use a newer feature. Accept the complete permission prompt, return to Connections, refresh the channel list, and run Save channel + test again.

Disconnect removes the workspace connection and stops PIWOT℗ from posting there. You can reconnect later, but you must confirm the workspace and notification channels again.

11

How PIWOT℗ protects workspace data

  • Only a signed-in PIWOT℗ Admin can start the connection
  • Slack webhooks and interactive actions are signature-checked
  • An unknown Slack workspace receives no board data
  • A Slack action can only change a request linked to that installation's organization
  • Installing the Slack app alone does not grant access to a PIWOT℗ workspace

FAQ