Skip to main content
Connect Slack and you can run Replo without leaving your workspace. @mention the Replo bot in a channel and it kicks off a full Replo session right there in the thread; it can edit your site, pull analytics, manage products and orders, and publish, then post the result back in the thread. It is the same Replo you use in the app. Slack is just another place to reach it, so your teammates can ship changes from the channel where they already work.

​
Connect Slack

1

Open the Integrations app

In Replo, open the Integrations app and find Slack.
2

Authorize Replo

Sign in to Slack and approve access. This links your Slack workspace to Replo and sets the project you connected from as the default. Workspace owners and members can change that default or add rules for specific conversations; see Choose which project handles it.
3

Add the bot to a channel

In Slack, invite the Replo bot to any channel you want to use it in. The bot only sees messages in channels it has been added to.

​
Trigger Replo from Slack

@mention the Replo bot in a channel, followed by what you want it to do. Write the same way you would in the Replo app; plain language works best.
The bot reacts with 👀 to show it picked up your request, then posts a reply in the thread and starts working. You do not need to format anything; just describe the outcome you want. A few more examples:

​
Follow the run in the thread

Once Replo is working, its reply updates live so you can watch progress without opening Replo:
  • The message renders as a live card: a title for what Replo is doing, and a running checklist of steps with icons for editing, analytics, publishing, and more, checked off as each one finishes.
  • An Open in Replo button deep-links to the session in the Replo app if you want to take over there.
  • A Stop generating button cancels the run from Slack.
When Replo needs a choice, it asks in the same thread. The card lists the options and a notice such as “I’ll keep moving with Bold in about 5 minutes. Pick another option if you’d prefer.” — always the first option. Answer before then. If there is only one option, the notice names it without asking you to pick another. Steps you already chose stay. If nobody answers in time, Replo continues with that first option and the card says “No answer in time, so I went with Bold”. Reply in the thread afterwards if you want something else. A free-text step has no options, so the card says “I’ll skip this step in about 5 minutes unless someone answers” up front and, after the wait, “No answer in time, so I skipped this step”. Approval prompts (publishing, checkout setup, and other permission cards) still wait for Allow always, Allow once, or Deny. They have no timer. When it finishes, Replo posts its final response in the thread and swaps the 👀 reaction for ✅. The reply names the project it acted on, so you can tell at a glance which store changed.

​
Choose which project handles it

If you work across projects, open the Slack connection in the Integrations app and use Routing to choose where new conversations run:
  • Team rules match a word or phrase in a conversation’s first message, from top to bottom. The first matching rule wins. Matching ignores capitalization.
  • Workspace default is used when no team rule matches.
Workspace owners and members can edit the workspace default and team rules. Routing only applies to a Slack conversation’s first message. Replies in an existing thread keep using that thread’s project. Changes to routing apply to new chats.

​
Threads and follow-ups

Each thread is its own conversation. Replying in the same thread continues the session, so Replo remembers what it just did and you can iterate:
Start a new thread (or a new top-level message) when you want a fresh session with no prior context. Replo also reads earlier messages and any images or files in the thread, so you can drop in a screenshot or reference a link from earlier and it will use them.

​
Who can use it

Anyone in the channel can @mention the bot, but they need access to the connected Replo workspace to actually run Replo. If someone who is not yet in the workspace triggers Replo, it pauses and asks a workspace owner to approve them. The owner gets a DM with an Approve access button; approving invites that person by email and lets them use Replo from Slack right away. They show up as invited in Replo until they sign in to the web app.

​
What Replo can do, and its limits

From Slack, Replo has the same capabilities it has in the app: building and editing pages, working with products, orders, and assets, reading analytics, and publishing. A few things to keep in mind:
  • The bot must be added to a channel before it can see messages there.
  • You have to @mention the bot for it to respond; it ignores messages that do not mention it.
  • Posting to Slack and other write actions ask for your approval the first time, so Replo never acts in your workspace unprompted. Choose Allow always to stop being asked for that same action, Allow once to approve just this run, or Deny to block it; see Approvals for how standing rules work.

​
Let Replo post back to Slack

Connecting Slack also works the other way around. From the Replo app, you can ask Replo to send messages, search channels, or look up people in your workspace using your connected account, for example posting a launch summary to #marketing after it publishes a page. See the Integrations app for how to point Replo at a connected tool with an @-mention.