Slack Automation, Approvals & Workflow Integration
Run Slack on autopilot. Keep the veto.
154 actions8 triggers
Messages fire, reminders get created, and channels get reconfigured before you've read what triggered them. Rills proposes every Slack action; you approve before anything ships.
Interactive. No signup. 14 days free · approvals always free.
Most automation fires first, asks later. Rills shows you the change before it ships.
Every consequential communication action from Slack arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.
Queue 3
Create 8 follow-up reminders for unanswered DM threads?
8 threads · no reply in past 72h
Same pattern as last Monday's follow-up run
3 threads involve active client accounts
Free to wait. Free to think.
Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.
Approve from your phone in five seconds.
Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, no 3am stomach-drop wondering what shipped while you slept.
Routine cases graduate themselves.
Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.
About Slack automation
Slack automation feels safe until something posts to the wrong channel at the wrong moment, or a reminder fires to a client before you knew it was going out.
When Slack runs unsupervised
One misconfigured trigger and messages go out to everyone, presence gets set incorrectly, or a channel gets unarchived at the worst possible time.
- SLACK_CHANNEL_MESSAGE_RECEIVED: A bot reads an inbound message and sends a reply that contradicts what your team already told the client.
- SLACK_DIRECT_MESSAGE_RECEIVED: An automated response fires into a DM thread where a sensitive negotiation is already in progress.
- SLACK_REACTION_ADDED: A reaction on a status message triggers a downstream action that posts a public update you hadn't signed off on.
- SLACK_RECEIVE_BOT_MESSAGE: A bot-to-bot handoff creates a reminder or opens a DM before anyone has verified the context is correct.
- SLACK_CHANNEL_CREATED: A new channel gets created and populated with participants before the name or purpose has been confirmed.
What Rills does inside Slack
Rills watches for the communication events that matter, then queues proposed actions like creating a reminder, setting a conversation topic, or sending an ephemeral message for your review before anything hits a channel or inbox.
The message still goes out; you just see it before it does.
When Slack events should and shouldn't act on their own
Not every trigger carries the same risk. Some Slack events are routine enough to graduate toward autonomous handling over time; others should always wait for your call.
- SLACK_CHANNEL_CREATED: Routine enough to automate once you've confirmed the naming and membership pattern a few times.
- SLACK_MESSAGE_REACTION_ADDED: Can be routine for internal emoji-based status signals, but needs a human when it drives any customer-facing communication.
- SLACK_RECEIVE_BOT_MESSAGE: Almost always needs a human; bot-sourced messages carry assumptions that are hard to verify without reading the thread.
- SLACK_DIRECT_MESSAGE_RECEIVED: Always wait for your approval when the proposed response involves pricing, commitments, or anything a client will screenshot.
- SLACK_REACTION_REMOVED: Low stakes on its own, but if it unwinds a workflow that already sent something, a human needs to confirm the reversal first.
What wakes Rills up in Slack
When these events fire, Rills proposes the next move and waits for your call.
SLACK CHANNEL MESSAGE RECEIVED
Fires when a message is posted in a Slack channel, including public, private, and multi-party conversations—but excludes direct messages. This is ideal for monitoring all team channel activity.
SLACK DIRECT MESSAGE RECEIVED
Fires when a user receives a direct message in Slack. Catches messages across all DM conversations with a single trigger.
SLACK MESSAGE REACTION ADDED
Fires when someone adds an emoji reaction to a message in Slack. You can optionally filter by specific channels or emoji types.
What Rills can do in Slack
2 of 154 actions across reads, writes, and updates.
- 01
Create channel
Creates a new public or private channel in your Slack workspace to organize team conversations around specific topics, projects, or departments.
- 02
Fetch conversation history
Retrieves a chronological list of messages from a Slack channel, allowing you to access conversation history with filtering by date range and pagination options.