Slack Integration
Connect your workspace to Slack so your team sees job activity where they already work. REMO posts team-ops notifications to your Slack channels, and your team can act on jobs — and ask REMO questions — without leaving Slack.
Connecting your workspace
An admin connects REMO to your Slack workspace from Advanced → Settings → Integrations → Slack.
- Go to Advanced → Settings → Integrations and open Slack.
- Click Connect Slack.
- Sign in to your Slack workspace and authorize the REMO app.
- Choose a default channel for team-ops notifications.
REMO installs as a Slack app with its own bot, so notifications and replies come from REMO rather than from a personal account. Once connected, the integration is ready — notifications start flowing to your default channel.
Connecting Slack requires Owner or Admin access to the workspace.
Team-ops notifications
When connected, REMO posts a card to Slack as jobs move through their lifecycle. The events that post are:
| Event | When it posts |
|---|---|
| New booking | A job is booked. |
| Staff assignment | A photographer or editor is assigned to a job. |
| Media received | Raw media has come in and the job is ready for editing. |
| Ready for delivery | Editing is complete and the job is ready to deliver. |
| Delivered | The job has been delivered to the client. |
Enriched cards
Every card carries the common job-identity fields so your team can tell jobs apart at a glance, without opening REMO:
- Property address for the job.
- Client name on the client-milestone cards (the booking, ready-for-delivery, and delivered events above).
- Order number and workspace name in the card footer (for example,
FP-00042 • Final Photo). - A deep link to the job's permalink, so anyone on the team can jump straight to the full job view in REMO.
The workspace name in the footer matters when more than one REMO workspace posts into the same Slack workspace — it's how your team tells which REMO workspace an event belongs to.
Per-event channel routing
By default, every enabled event posts to your default channel. You can also route individual events to their own channels.
On the Notifications card in Slack settings, each event row has:
- A toggle to turn that event's notifications on or off.
- A channel picker to send that event to a specific channel instead of the default.
Leave the picker on Default channel to keep an event on your default, or pick another
channel to override it. For example, you might send Ready for delivery to a
#deliveries channel while everything else stays in your default.
The channel picker works whether or not the event is enabled. A channel you set on a disabled event is simply remembered and used once you turn the event back on.
/remo slash commands
Your team can pull job information into Slack on demand with the /remo command:
| Command | What it does |
|---|---|
/remo today | Lists today's jobs. |
/remo unassigned | Lists jobs that still need a photographer or editor. |
/remo job <address> | Looks up a job by its property address. |
/remo help | Shows the available commands. |
Where a reply lands depends on the command. The day's schedule, unassigned-jobs results,
and the help card (/remo today, /remo unassigned, /remo help) post into the
channel, so anyone there sees them and you can pin or share them. Job look-ups
(/remo job <address>), usage hints, not-found and error messages, and a bare /remo
reply privately to just you, so a stray keystroke doesn't broadcast.
REMO matches the person running the command to their workspace member by their Slack email, so commands respect what that person is allowed to see.
Interactive buttons
Some notification cards include action buttons so your team can move a job forward right from Slack:
- Mark Delivered — marks the job as delivered to the client.
- Confirm Editor — confirms the suggested editor assignment for the job.
Clicking a button performs the action in REMO and updates the card. As with slash commands, REMO identifies who clicked by their Slack email and applies their permissions.
Recent activity viewer
Admins can review what REMO has posted and answered without leaving the settings page. The Slack settings page includes a Recent activity section showing the most recent notifications and command responses, each marked as a success or failure (with the error when something didn't go through). It's the quickest way to confirm an event reached Slack or to spot a misconfiguration.
Asking REMO in Slack
Beyond slash commands, you can mention @REMO in a channel to ask about your workspace in plain language, and REMO answers in the thread from your live data. See The @REMO Slack agent for what it can answer and how to enable it.
Sharing one Slack across workspaces
More than one REMO workspace can connect to the same Slack workspace — for example, a parent company whose Slack hosts channels for several REMO workspaces.
Outbound notifications are always isolated: each REMO workspace posts to its own configured channels, and the workspace name in every card footer keeps the source clear.
Inbound actions — @REMO mentions, /remo commands, and button clicks — are
channel-scoped. REMO resolves which workspace an action belongs to from the channel it
came from (the workspace that posts to that channel), so a request in one workspace's
channel is always handled by that workspace.
A direct message from someone who belongs to only one connected workspace resolves normally — REMO answers as that workspace. The ambiguity handling only kicks in at the edges: if a channel isn't tied to a single workspace, or a direct message comes from someone who belongs to more than one of the connected workspaces, REMO declines gracefully and asks you to use that workspace's channel, rather than guessing and answering as the wrong workspace.