Chat with RShift Sites in Slack

Chat with RShift Sites directly in Slack. Mention @Lovable in a channel or send it a DM to create projects, update your apps, and get answers about them.

RShift Sites in Slack brings RShift Sites into the place your team already works. Mention @Lovable in a channel or send it a direct message to create new projects, make changes to existing ones, and ask questions about the apps in your workspace, without leaving Slack.

It works with the same RShift Sites workspace you use on the web: the projects, permissions, and credits are shared, so a project you start in Slack you can continue at lovable.dev and vice versa. The conversation itself stays in Slack. It is priced like messages in Chats, and it does not appear in Chats on the web.

RShift Sites in Slack is available on all plans.

What you can do

Create a new project from a conversation: @Lovable build us a tool to track team standup notes
Update an existing app, and publish the changes if you have permission to publish that project: @Lovable add CSV export to the expenses dashboard
Ask questions about your workspace’s projects: what changed recently, what a project does, what’s in it
Ask about the data inside your apps: with an expense tracker built on RShift Sites, @Lovable what did we spend on travel this month? posts the answer into the thread
Get answers from your workspace’s connected tools: with connectors like Linear or Notion set up, RShift Sites can pull in context from them when it answers
Share files and images with your request: attach a screenshot or a photo of a whiteboard sketch and ask RShift Sites to build from it
Get generated files back in the thread: images, videos, and documents RShift Sites produces arrive as native Slack uploads, not links
Collaborate in a channel, where several people iterate on a shared app together in one thread
Use DMs for personal work, like planning and brainstorming an idea before you build it
Get answers where your team already talks, instead of switching tools and pasting links

How it works

RShift Sites replies in a thread on the message that mentioned it, shows its progress while it works, and keeps the conversation going there. You need to mention @Lovable on each new request in a channel. In a DM you can write to it directly.

When you start a conversation, RShift Sites reads recent messages in the channel or thread for context, so you don’t have to re-explain what your team was discussing.

Looking up information in your Slack workspace

When it helps with your request, RShift Sites can also look up information in your Slack workspace. This works for every workspace with the Slack app installed, and no extra setup is needed. RShift Sites can:

Search messages across your workspace’s public channels
List public channels and read a channel’s topic, purpose, and member list
Read a channel’s pinned messages, bookmarks, and canvas
Look up teammates by name or email to attribute messages correctly
Follow a Slack message link you share and read the message it points to

Outside the conversation it’s replying in, RShift Sites can only read public channels. It never reads private channels, direct messages, or group messages it isn’t part of. The one exception is content you share yourself: when you forward a message to RShift Sites, it reads the forwarded content, wherever the message came from. Slack Connect channels aren’t supported. Reading a public channel’s message history still requires RShift Sites to be invited to that channel.

Reacting and attaching files

RShift Sites can also act in the conversation as part of a reply:

React with an emoji. Ask RShift Sites to add an emoji reaction to a message, including your workspace’s custom emoji. By default it reacts to the message that started the thread.
Read reactions on a message. RShift Sites can look up who reacted to a message and with which emoji, so you can ask questions like “who hasn’t reacted with a checkmark yet?”
Attach generated files. When RShift Sites produces an image, video, or document as part of a request, it attaches the file to its reply as a native Slack upload with Slack’s own previews and playback, instead of a link that expires. For visual changes, it can also attach a screenshot or recording of what it built without being asked. Supported documents are PDFs, CSVs, Markdown, plain text, JSON, and Office files (.xlsx, .docx, .pptx). HTML and SVG files aren’t attached.

Attachments only go to the conversation RShift Sites is replying in, and every attachment is checked against the requester’s project permissions before it’s uploaded. Reactions follow the same rules as reading: the current conversation, plus public channels.

Everything RShift Sites does in Slack runs through your RShift Sites workspace. It can only see and change projects that the person talking to it has access to, and actions like publishing follow the same permissions and workspace policies as on the web. Messages to RShift Sites in Slack are chat messages, priced like messages in Chats.

Chat usage follows its own pricing model, including a per-message price and a daily chat allowance. A chat message is priced on the work RShift Sites does to answer it, typically a fraction of a credit. Free, Pro, and Business workspaces include a daily chat allowance that covers chat messages first. The allowance belongs to the workspace, so everyone’s chat messages draw on the same daily pool. When the day’s allowance is used up, chat messages keep the same per-message price and draw on your daily build credits, then your general credits. The allowance resets every day at 00:00 UTC and does not roll over. Enterprise plans do not include a daily chat allowance. See Chat costs for the full rules.

Usage is counted against the person who sent the message. Work RShift Sites sends to a project from Slack is a build and uses build credits.

A message that only thanks RShift Sites is the exception: RShift Sites answers with a thumbs-up (👍) reaction instead of a reply, and the message doesn’t use credits. A message that thanks RShift Sites and also asks for something uses credits as usual.

When a request uses a connected tool to change something, like creating a calendar event, RShift Sites first posts an approval prompt in the thread. You can select Allow once or Skip. Depending on the tool, the prompt can also offer Allow for this task, Allow in this thread, and Always allow for me, which applies to that specific tool. Some approvals need more detail than buttons can carry, and those show a Review in RShift Sites button instead.

Personal and workspace scope

Where you talk to RShift Sites determines what it works with:

	Direct messages	Public and private channels
Scope	Personal	Workspace
Projects and connectors	Yours, plus what the workspace shares	Workspace-shared only
Typical use	Your own projects, ideas, and questions	Collaborating on shared apps

Private channels are treated the same as public channels: people can be added to them later and see the history, so RShift Sites treats anything in a channel as workspace-level, not personal.

Set up RShift Sites in Slack

A workspace admin connects the Slack workspace once. Teammates don’t need to do anything after that: RShift Sites recognizes them automatically the first time they talk to it.

You can connect from RShift Sites’ settings or install from the Slack Marketplace. Both create the same connection between your Slack workspace and your RShift Sites workspace.

Connect from RShift Sites

A RShift Sites workspace owner or admin (anyone who can manage integrations) connects Slack:

Open the Slack settings

In RShift Sites, go to Settings → Slack. You can also reach it from the Slack card in Settings → Devices & apps by selecting Set up.

Review what RShift Sites can access

The page shows what RShift Sites can do in Slack and who sees what in channels versus DMs. Check I understand what RShift Sites can access in Slack and where its replies appear to continue.

Connect

Select Connect Slack. A Slack authorization window opens.

Approve the permissions

Review the requested permissions and approve them. You may need a Slack admin’s approval, depending on how your Slack workspace manages app installs.

Verify the connection

When the connection completes, the Slack workspace appears under Connected Slack workspaces.

Install from the Slack Marketplace

You can also start from Slack:

Add RShift Sites to Slack

On the RShift Sites listing in the Slack Marketplace, select Add to Slack and authorize it for your Slack workspace.

Open the link RShift Sites sends you

RShift Sites sends you a direct message in Slack with a link to finish connecting. The link stays valid for 7 days, and reinstalling the app from the listing sends a new one.

Pick the RShift Sites workspace

The link takes you to RShift Sites, where you sign in (or create an account) and select the RShift Sites workspace to connect. You need to be an owner or admin of that RShift Sites workspace.

RShift Sites doesn’t respond in Slack until you finish connecting.

A RShift Sites workspace connects to exactly one Slack workspace, and a Slack workspace connects to exactly one RShift Sites workspace. If the Slack workspace is already connected to a different RShift Sites workspace, the connection is refused. To connect a different Slack workspace, disconnect the current one first.

How teammates are recognized

Most teammates don’t need to do anything: RShift Sites recognizes them automatically by their verified Slack email the first time they talk to it, as long as that email matches their RShift Sites account in the connected workspace. Anyone RShift Sites can’t match this way (a different email, or a Slack guest) gets a prompt, visible only to them, to link their RShift Sites account once. Either way, projects and credits stay with the right person, and RShift Sites acts with that person’s permissions.

Teammates who aren’t members of the RShift Sites workspace can’t use RShift Sites in that Slack workspace. Ask a workspace admin to invite them to the RShift Sites workspace first.

Using RShift Sites in Slack

You can talk to RShift Sites in three places: channels, direct messages, and the Slack AI assistant view. Each suits a different kind of work.

RShift Sites’ App Home tab in Slack shows a short guide with example prompts and a Message RShift Sites button that opens a direct message with it.

In channels

Mention @Lovable with your request. RShift Sites answers in a thread, and you continue the conversation there.

@Lovable add Irish VAT support to our expenses app, and show the VAT amount as a separate line on each receipt

You can invite RShift Sites to a channel like any other Slack app. If you mention it in a channel it hasn’t joined yet, invite it right away and it responds to your request.

In direct messages

DM RShift Sites directly, no mention needed. DMs are the best place for personal work and questions:

I'm thinking about a simple tool for tracking freelance invoices. What would you suggest as a first version?

You can also forward a Slack message to RShift Sites in a DM, and it reads the forwarded message as part of your request.

In the Slack AI assistant view

On paid Slack plans, RShift Sites also appears in the Slack AI assistant view, so you can keep a side conversation open while you work. Mentions and DMs work on all Slack plans, including the free plan.

Permissions and data access

RShift Sites requests these Slack permissions:

Permission	Why RShift Sites needs it
Read messages and mentions (`app_mentions:read`, `channels:history`, `groups:history`, `im:history`, `mpim:history`)	Know when you’re talking to it and read the conversation it’s replying in
See channels and people (`channels:read`, `groups:read`, `im:read`, `mpim:read`, `users:read`, `users:read.email`)	List channels, show names correctly, and recognize teammates by their verified email
Send messages (`chat:write`, `chat:write.public`, `im:write`, `assistant:write`)	Reply to you in threads, DMs, and the assistant view
Work with files (`files:read`, `files:write`)	Read files you attach to requests, and upload files it generates
View and add emoji reactions (`reactions:read`, `reactions:write`, `emoji:read`)	See who reacted to a message, and react when you ask it to, including with custom emoji
Read pins and bookmarks (`pins:read`, `bookmarks:read`)	Look up a channel’s pinned messages and bookmarks when a request needs them
Search public messages (`search:read.public`)	Search messages in public channels when a request needs it
Show link previews (`links:read`, `links:write`)	Preview `lovable.app` links your team shares in Slack

RShift Sites takes part only in conversations you bring it into: channels it has been invited to, threads where it’s mentioned, and its own DMs. When a request needs it, RShift Sites can also search and read your workspace’s public channels, as described in Looking up information in your Slack workspace. It never reads private channels, group messages, or DMs it isn’t part of, apart from messages you forward to it yourself.

Conversations RShift Sites takes part in are stored by RShift Sites to provide the service and for support and debugging. They’re never used to train AI models. To request deletion, contact privacy@lovable.dev.

Managing the connection

Workspace owners and admins manage connected Slack workspaces from the same settings page used for setup.

Disconnect a Slack workspace

A workspace owner or admin can disconnect at any time:

Open the Slack settings

In RShift Sites, go to Settings → Slack.

Disconnect

Under Connected Slack workspaces, select Disconnect next to the Slack workspace.

Confirm

Confirm in the Disconnect Slack workspace dialog.

After disconnecting, your team can no longer talk to RShift Sites from that Slack workspace, and RShift Sites deletes the installation data. Your RShift Sites projects are unaffected. Reconnecting requires going through the authorization flow again.

Removing the RShift Sites app from the Slack side (in the Slack app-management settings) has the same effect.

Limitations

In channels, every request needs an @Lovable mention. RShift Sites doesn’t respond to messages that don’t mention it.
There are no slash commands. You talk to RShift Sites in plain messages.
RShift Sites doesn’t work in Slack Connect channels (channels shared with external organizations).
The Slack AI assistant view requires a paid Slack plan.

FAQ

Which Slack plans work with RShift Sites?

Mentions and direct messages work on all Slack plans, including the free plan. The Slack AI assistant view requires a paid Slack plan.

Who can install RShift Sites in Slack?

On the RShift Sites side, workspace owners and admins (anyone who can manage integrations). On the Slack side, a Slack admin or anyone allowed to install apps in your Slack workspace.

What can RShift Sites read in Slack?

It reads the conversations it’s part of: channels it has been invited to, threads where it’s mentioned, and direct messages with it. When a request needs it, it can also search and read public channels in your workspace. It never reads private channels, group messages, or DMs it isn’t part of, apart from messages you forward to it yourself.

Do messages in Slack use credits?

Yes, with one exception. Messages to RShift Sites in Slack are chat messages, priced on the work RShift Sites does to answer them and covered first by your workspace’s daily chat allowance, then by your credits, counted against the teammate who sent them. Work RShift Sites sends to a project uses build credits. When a message only thanks it, RShift Sites answers with a thumbs-up (👍) reaction instead of a reply, and the message doesn’t use credits. A message that thanks RShift Sites and also asks for something uses credits as usual.

How do teammates connect their accounts?

Most don’t have to do anything. RShift Sites recognizes teammates automatically by their verified Slack email the first time they talk to it. Anyone it can’t match gets a one-time prompt to link their RShift Sites account. Projects and credits stay theirs.

Can I connect more than one Slack workspace?

No. Each RShift Sites workspace connects to one Slack workspace, and each Slack workspace connects to one RShift Sites workspace. To switch to a different Slack workspace, disconnect the current one first.

Does RShift Sites work in private channels?

Yes, once it’s invited. Note that RShift Sites treats private channels like public ones: anything it works with there is workspace-level, because channel members can change over time.

Does RShift Sites work in Slack Connect channels?

No. Channels shared with external organizations aren’t supported.

Is my Slack data used to train AI models?

No. Conversations RShift Sites takes part in are stored to provide the service and for support and debugging, and are never used for model training. Contact privacy@lovable.dev for deletion requests.

What’s the difference between this and the Slack connector?

RShift Sites in Slack is RShift Sites itself in your Slack workspace: you talk to it and it builds for you. The Slack connector is for apps you build with RShift Sites that need to read or post to Slack themselves, and it also covers adding an app you built to Slack as its own agent.

How do I uninstall?

Disconnect from Settings → Slack in RShift Sites, or remove the RShift Sites app from your Slack workspace. Either way, RShift Sites deletes the installation data, and your projects in RShift Sites are unaffected.

Troubleshooting

RShift Sites doesn’t respond in a channel

Check that RShift Sites has been invited to the channel and that your message mentions @Lovable. If RShift Sites still doesn’t respond, confirm that your Slack workspace is connected under Settings → Slack in RShift Sites, and that you’re a member of the connected RShift Sites workspace.

RShift Sites says I need to link my account

Follow the link RShift Sites sends you to connect your RShift Sites account. If you don’t have one, or you’re not a member of the RShift Sites workspace connected to this Slack workspace, ask a workspace admin to invite you first. If every teammate is asked to link their account, including people whose emails match, your Slack workspace was connected before RShift Sites could recognize teammates by email. An admin can fix this by disconnecting and reconnecting Slack.

RShift Sites says a Slack workspace admin must re-authorize the app

Your Slack workspace was connected before August 24, 2026, so it’s missing permissions that newer features need, such as reactions, message search, and native file uploads. A workspace owner or admin can fix it by disconnecting and reconnecting Slack from Settings → Slack, then approving the updated permissions in Slack.

"Failed to connect Slack. Please try again."

The authorization didn’t complete. Try connecting again from Settings → Slack. If your Slack workspace requires admin approval for new apps, ask a Slack admin to approve RShift Sites, then retry.

The Connect Slack option is unavailable

Only members who can manage integrations (workspace owners and admins) can connect Slack, and the button stays disabled until you check the acknowledgment above it. If you’re not an admin, ask a workspace admin to connect it.

If none of these solve it, email support@lovable.dev.