Terra in Slack
Bring Terra into your team's Slack channels, how a thread becomes a chat, what Terra answers and what it stays out of, and where the work shows up in your dashboard.
Terra can work from your team's Slack channels. You @mention it, it replies in the thread, and the same conversation appears in your dashboard with everything it built. Nobody has to leave Slack to ask for a change, and nobody loses the record of it.
Setting it up
An org admin connects the workspace once.
- In the dashboard, open your brand and go to Integrations.
- Under Terra in Slack, click Add to Slack and authorize.
- In Slack, invite the bot to a channel:
/invite @Terra.
Terra only sees channels it has been invited to. There is no way for it to read a channel it is not a member of, and it does not do DMs.
"Terra in Slack" is not the same as the Slack integration in your connected accounts. This one puts Terra in your channels as a bot. The other one connects Slack on your own behalf so Terra can act as you. Connecting one does nothing for the other.
Connecting a channel to a brand
The first time you mention Terra in a channel, it links that channel to a brand.
- With one brand in your workspace, it links automatically and gets to work.
- With several, Terra asks which brand this channel is for and posts a picker in the thread. Choose once, and the channel stays connected to that brand.
Every channel can point at a different brand, so a team running three sites can keep three channels and never think about it again.
How a conversation works
Mention Terra to start:
@Terra add a pricing FAQ to the product pageWhat follows is the same every time:
- 👀 within a few seconds. Terra saw the message and took the work.
- A short "On it." reply in the thread, which turns into the answer when the work is done. It edits that same message rather than posting a second one, so the thread stays readable.
- The answer, in the thread, when the turn finishes.
A thread is one conversation. Once Terra is in a thread, reply normally without mentioning it again and it keeps up. Start a new thread when you want a fresh piece of work.
What Terra replies to, and what it stays out of
A channel with Terra in it is still your team's channel. The rules are deliberately narrow:
| In the channel | Terra's behavior |
|---|---|
| You @mention Terra | Replies, and opens a thread as the conversation |
| A plain reply in a thread Terra is already in | Replies, no mention needed |
| A message mentioning a colleague and not Terra | Stays out of it, even inside its own thread |
| Any message in a channel Terra was never invited to | Never sees it |
| General chatter outside a Terra thread | Ignores it |
The third row is the one worth remembering: if you write "@Priya can you check this?" inside a Terra thread, Terra treats it as your conversation, not its own. Mention Terra again when you want it back.
Sending screenshots
Post an image with your message and Terra looks at it.
@Terra the hero looks cramped on mobile, see attachedIt reads the image as part of that first reply, and can look again later in the thread if you ask about a detail it did not mention. Up to four images per message. Very large files are skipped, and Terra says so plainly rather than pretending it saw something.
Answering Terra from Slack
When Terra needs a decision, it asks in the thread rather than waiting somewhere you cannot see.
- A question with a few options arrives as a dropdown.
- Something needing approval arrives with Approve and Decline buttons.
- An open-ended question arrives with a link to the chat in your dashboard, since that is a better place to type a long answer.
Answer it in Slack and the message updates in place with the outcome and who decided. The dashboard shows the same result, because it is the same conversation.
Where the work shows up
Every Slack thread is a real chat in your dashboard, listed with a slack label and the name of whoever started it. Open it and you get the full picture: the messages from Slack, Terra's replies, and the preview of everything it built.
That matters because Slack is a good place to ask and a poor place to review. Ask in the thread, then open the chat to look at the pages, edit them, or publish.
What to expect
Replies take as long as the work takes. A question about your site comes back quickly. Building a page runs for minutes. The "On it." message is there so you can tell the difference between working and stuck.
One reply per request. Terra answers when the turn is complete rather than narrating each step. Send two messages quickly and it may fold them into a single answer covering both.
Long answers arrive in a few messages. Slack caps message length, so Terra splits at natural boundaries rather than truncating.
Everyone in the channel can talk to Terra. Channel membership is the permission model: if someone can see the channel, they can ask Terra for work on the connected brand. Invite it to channels whose membership you would trust with that brand's site.
Disconnecting
Disconnect the workspace from the same Integrations page. Terra loses access immediately and stops replying within a minute. The chats it already created stay in your dashboard, so the record of the work survives the disconnection.
Current limits
- Channels only. No DMs, and no slash commands yet.
- Terra speaks when spoken to. It cannot start a thread on its own, so a scheduled playbook finishing will not announce itself in Slack.
- No threading across channels. A conversation lives in the thread it started in.
Last updated on