Slack (Beta)

Review requests, make decisions, and follow the results in Slack. ActionBox applies the same permissions, reviewer restrictions, and deadlines you use on the web and mobile.

Before you connect

• You need an ActionBox account and membership in the workspace you want to connect.
• An ActionBox owner or admin installs the integration. Your Slack workspace may also require an owner or administrator to approve the app.
• Each ActionBox workspace connects to one Slack workspace.

You do not need to create a Slack app or handle app credentials.

Set up Slack

1. Connect the workspace

After arranging beta access:

1. In ActionBox, open Settings → Slack (Beta).
2. Choose Connect Slack.
3. Check that you have selected the intended Slack workspace, then approve the installation.

Start from ActionBox Settings so the installation connects to the correct ActionBox workspace.

2. Link your account

Each reviewer completes these steps:

1. Open the ActionBox app in Slack and choose Connect account, or run /actionbox link.
2. Sign in to ActionBox. Check the account name and both workspace names in the confirmation.
3. Return to Slack and confirm your account link in the private message.

Installing the app does not link everyone automatically. Matching email addresses do not grant access.

Find requests

Open the ActionBox app's Home tab. Choose Mine, Unassigned, All visible, Snoozed, or History. You can search Action titles and filter by Source or priority.

All visible only includes Actions your account can access. Home is also useful when you have paused notifications or want to check work you missed.

Review the context

Each request appears in a bordered Slack card. The card leads with the question, followed by a short explanation and key facts when supplied. Choose View details to read the full evidence. Controls and management options are under More actions in the detail view.

Code and diffs keep their text. Slack does not reproduce the mobile app's syntax highlighting or every layout detail.

Respond to a request

Choose a response, then submit the confirmation or response form. Supported types include boolean, choices, text, numbers, ratings, and forms. If a response cannot be represented accurately in Slack, choose Open ActionBox to finish on the web.

The confirmation window updates when ActionBox has checked your request. It shows whether the request was applied and lets you reopen the details. You can close it while processing; your private conversation also receives the result.

After you respond, the card shows:

• Who responded and what they answered.
• The recorded reason, when supplied.
• The time and, when available, whether the response came from Slack, web, or mobile.

Your own responses are marked you.

Follow the history

Each Action has a Slack thread with matching cards for decisions, comments, context requests, assignment changes, and control results. New control runs use one thread entry that updates as the operation progresses. It keeps the requester visible alongside the latest status; older conversations may have separate entries for each stage. Open View details → Activity & comments to review the Action's history. Longer content is available in the detail view.

To leave an ActionBox comment, choose View details → More actions → Add comment. Text typed directly into a Slack thread stays in Slack; it is not added to ActionBox history.

Use controls and manage work

Open View details → More actions to use an Action Control. It requests the operation declared by the Source. Destructive controls ask for confirmation. Check the resulting control status and any verification result: a queued or accepted request does not mean the external operation succeeded.

Under More actions, you can also:

• Request more information or add a comment.
• Claim an Action or snooze it.
• Change assignment or edit eligible reviewer lists if you are an owner or admin.

Snoozing affects everyone reviewing the Action and does not extend its deadline. Your existing role and reviewer restrictions apply to every operation.

Choose notifications

Run /actionbox settings to manage DMs, optional unassigned alerts, reminders, and escalations. Your ActionBox quiet hours apply to Slack notifications.

Send requests to a channel

An owner or admin can set a workspace default channel or a separate destination for a Source:

1. Invite ActionBox to an internal Slack channel.
2. In ActionBox Settings → Slack (Beta), choose the Source or workspace default.
3. Select a destination channel and choose Save destination.

The list includes internal channels the app has joined. Use Find a channel to search the loaded names, Load more channels for additional results, or Refresh channels after inviting the app. If needed, expand Use a channel ID instead and paste the ID from Slack’s channel details.

Routing changes affect new messages. Existing Action messages stay in their original destination.

Decide what the channel can see

Channel cards start with a minimal summary. An owner or admin can enable these settings separately for each saved route:

Anyone who can read the channel can read this content. Restricted Actions are never posted to channels. Slack Connect and shared channels are outside the beta.

Changing a sharing setting updates existing tracked messages while ActionBox still has Slack access.

Keep Actions out of Slack

Exclude a Source

In Settings → Slack (Beta) → Sources available in Slack, turn off the Source. Its Actions are excluded from channel messages, DMs, private details, and Home.

Exclude an individual Action

API integrations participating in the beta can use:

An update that changes only the delivery policy can also exclude a completed Action without changing its decision. This is a beta API field. Confirm that your workspace and API or SDK version support it before adding it to your integration.

ActionBox tries to update existing messages. Slack exports, retained copies, screenshots, and notifications already delivered cannot be recalled.

Troubleshooting

Unlink or disconnect

Choose Unlink my account to remove your personal link. Workspace owners and admins can disconnect the entire integration.

ActionBox tries to clear its messages while it still has access. Removing or revoking the app inside Slack can prevent that cleanup.