Turn Slack conversation history into a BotMape follow-up
Set a regular review of a relevant Slack conversation, then ask Notis to surface BotMape-related questions, decisions, or follow-ups found in the available messages.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Fetch conversation history
Fetches a chronological list of messages and events from a specified slack conversation, accessible by the authenticated user/bot, with options for pagination and time range filtering.
Why this helps
Important agent questions and decisions get buried in Slack history, leaving you to reread long threads when it is time to follow up.
- Review conversation history on a predictable schedule.
- Surface BotMape-related decisions and unresolved questions from available messages.
- Send the review to a chosen Notis report channel.
Setup
Build it in a few focused steps.
- 1Connect BotMape and Slack once in the Notis portal.
- 2Create an automation and describe the BotMape-related review you want from Slack history.
- 3Choose a recurring schedule as the trigger.
- 4Choose where Notis should send run reports.
- 5Test with one real Slack conversation review and refine the instruction.
Questions about this workflow
Does BotMape start this workflow?
No. BotMape exposes no trigger events in this workflow context. A recurring Notis schedule starts the run, and Notis retrieves Slack conversation history as an action.
Will it read every Slack conversation?
The Slack action retrieves history for a specified conversation that the connected account can access. Identify the relevant conversation in your automation instruction.
Can it identify decisions that are missing from the conversation?
Notis can analyze the available history, but it cannot infer facts that were never shared. Provide any needed BotMape context in your instruction or the conversation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BotMape to Slack. A trigger fires from one place; an action lands in another.
BotMape triggers
Slack actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Set snooze duration
Deprecated: turns on do not disturb mode for the current user, or changes its duration. use `set dnd duration` instead.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add a custom emoji to a Slack team
Deprecated: adds a custom emoji to a slack workspace given a unique name and an image url. use `add emoji` instead.
Add an emoji alias
Adds an alias for an existing custom emoji in a slack enterprise grid organization.
Add a remote file
Adds a reference to an external file (e.g., google drive, dropbox) to slack for discovery and sharing, requiring a unique `external id` and an `external url` accessible by slack.
Add a star to an item
Stars a channel, file, file comment, or a specific message in slack.
Add call participants
Registers new participants added to a slack call.
Add emoji
Adds a custom emoji to a slack workspace given a unique name and an image url; subject to workspace emoji limits.
Add reaction to message
Adds a specified emoji reaction to an existing message in a slack channel, identified by its timestamp; does not remove or retrieve reactions.
Connect any two apps with Notis in the middle.
BotMape and Slack, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Slack.