Skip to content
Notis

Get a clear Slack alert when Brex spend needs attention

Send a Brex spend exception into Slack with the key details and a practical next step, so it is easier to act without reopening several tabs.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

Post message to channel

Deprecated: posts a message to a slack channel, direct message, or private channel. use `send message` instead.

Why this helps

Spend exceptions can disappear into a queue while the team is focused elsewhere, leaving founders to remember which transaction needs review.

  • Bring a flagged spend item into the team's existing conversation space.
  • Summarize the merchant, amount, and relevant context in one message.
  • Make the requested follow-up visible without manually rewriting transaction details.

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 give it a clear name.
  • 3In one instruction, ask Notis to review the incoming Brex spend exception and post its key details and next step in Slack.
  • 4Choose a webhook trigger and select where Notis should send run reports.
  • 5Test with one real Brex spend exception and check the Slack message for accuracy.

Questions about this workflow

What starts this automation?

A Notis webhook starts it when an HTTP request arrives. Brex does not expose a trigger event in this workflow context, so the webhook payload must provide the spend exception or transaction details.

Does the automation approve or change the Brex transaction?

No. This workflow posts a Slack message for review and follow-up; it does not approve, reject, or modify Brex data.

What if the webhook does not include a merchant or amount?

Notis can only summarize details present in the request or otherwise provided to it. Include the needed transaction context in the webhook payload.

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.

TriggerScheduled

Set snooze duration

Deprecated: turns on do not disturb mode for the current user, or changes its duration. use `set dnd duration` instead.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

Add an emoji alias

Adds an alias for an existing custom emoji in a slack enterprise grid organization.

ActionInstant

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.

ActionInstant

Add a star to an item

Stars a channel, file, file comment, or a specific message in slack.

ActionInstant

Add call participants

Registers new participants added to a slack call.

ActionInstant

Add emoji

Adds a custom emoji to a slack workspace given a unique name and an image url; subject to workspace emoji limits.

ActionInstant

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.

ActionInstant

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.