Review cards in Slack

When a build is ready, a card lands in your channel with a preview link and three buttons. It does exactly what the task board does.

You do not have to open the app to decide on a build. The card in your channel carries the same actions as the board, and calls the same logic, so the two cannot drift apart.

What the card contains

What changed, in plain language.
A Preview changes button that opens the draft theme.
Three action buttons: Approve & Publish, Comment, Reject.

Open the preview first. Reviewing a build explains what to look at.

Approve & Publish

Marks the task done and replies in-thread with the Shopify theme editor link.

Slack asks you to confirm before it runs.

It does not go live

This does not put the theme on your storefront. Queue an A/B test first, then open the theme in your Shopify admin and publish it there.

Comment

Opens a short form. Your note lands on the task thread and notifies the team, exactly as a comment in the web app does.

The agent iterates on the same draft theme, so your preview link keeps working.

Reject

Sends the task back to the backlog and rolls back this implementation attempt. The idea itself survives.

The form also takes an optional reason. Write one — it is the fastest way to stop the same mistake twice. The web app has nowhere to type this, so the Slack form is the better place to reject from.

After you decide

The buttons are replaced by the resolved state, so nobody can action the same card twice. The action is recorded against the Slack user who clicked it.

Safety

A card's buttons carry only the task's id. The store is always resolved from the channel binding, never from the message. A task id from another store is rejected.

Interactivity is a separate Slack configuration from events. If preview links work but buttons do not respond, tell your HI Engine contact — the app's interactivity endpoint needs checking on their side.