Check Slack conversation history while reviewing Brex spend
Bring relevant conversation history alongside a Brex transaction review, so the purpose or follow-up may already be documented where the team works.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
A transaction can be clear in Brex but still require searching Slack for the decision or business context behind it.
- Reduce the back and forth between transaction review and Slack search.
- Bring chronological messages from a specified conversation into the review.
- Make missing context easier to identify before deciding on a follow-up.
Setup
Build it in a few focused steps.
- 1Connect Brex and Slack once in the Notis portal.
- 2Create an automation in Automations, New Automation, and describe the transaction review you want to support.
- 3In one instruction, ask Notis to use the incoming Brex transaction details to retrieve history from a specified Slack conversation and summarize relevant context.
- 4Choose a webhook trigger and a destination for run reports.
- 5Test with one real transaction and confirm the conversation and time range provide useful context.
Questions about this workflow
Can this search every Slack conversation automatically?
The listed Slack action retrieves history for a specified conversation. The instruction or incoming request needs to identify a conversation that the connected account can access.
Does Slack history prove why a transaction happened?
No. It can provide context from messages, but the messages may be incomplete or ambiguous. Use the results as review context, not as proof or approval.
What does the Brex webhook need to include?
Include enough transaction information to identify what is being reviewed and, if needed, the Slack conversation to inspect. Notis cannot infer an unavailable channel identifier or conversation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Brex to Slack. A trigger fires from one place; an action lands in another.
Brex 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.
Brex 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.