Keep Brex spend follow-ups from slipping with Slack reminders
Ask Notis to check spend items on a schedule and turn clear, actionable follow-ups into Slack reminders with a useful due time.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Create a reminder
Creates a slack reminder with specified text and time; time accepts unix timestamps, seconds from now, or natural language (e.g., 'in 15 minutes', 'every thursday at 2pm').
Why this helps
Reviewing a transaction is only part of the work; unanswered questions and promised follow-ups can be forgotten after the initial check.
- Create a concrete nudge from a spend follow-up that might otherwise be forgotten.
- Keep follow-up reminders in Slack, where the team can see them.
- Use dates or timing rules supplied by the team rather than guessing deadlines.
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 name it for follow-up review.
- 3In one instruction, ask Notis to identify actionable Brex spend follow-ups and create a Slack reminder only when a due time is available or supplied.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real follow-up and verify its reminder text and time in Slack.
Questions about this workflow
Will Notis guess when a follow-up is due?
No. The instruction should ask Notis to use a date or timing rule present in the available data or supplied by you. If timing is missing, it should report that rather than invent one.
What kind of item should become a reminder?
Use a specific pending action, such as requesting missing transaction context. The workflow should avoid creating reminders for items that have no clear next step.
Does the schedule itself provide a due date?
The schedule controls when Notis reviews available spend. A reminder's time should come from an explicit due time or rule provided in the data or instruction.
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.