Fetch Brex transaction details from an incoming request
Send a transaction ID to Notis and get the Brex details in a run report for review.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Transaction by ID
Get details of a specific transaction by id.
Why this helps
When a transaction question arrives through another process, finding its record manually adds delay and breaks focus.
- Start a targeted lookup from an existing HTTP request.
- Avoid searching a full transaction list for one record.
- Route the result to a report channel for follow-up.
Setup
Build it in a few focused steps.
- 1Connect Brex once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name the transaction lookup.
- 3Tell Notis to retrieve the Brex transaction details for the transaction ID supplied by the incoming request.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test by sending one real transaction ID and review the returned details.
Questions about this workflow
Where does the transaction ID come from?
The calling process must supply it in the webhook request. This workflow does not discover an ID on its own.
Does the webhook change the transaction?
No. The Brex action retrieves transaction details only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Brex. A trigger fires from one place; an action lands in another.
Google Drive triggers
Brex actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Budget
Create a new budget for departments or projects.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Card
Create a new card and assign it to a user.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
Create Department
Create a new department.
File Created
Triggers when a new file is created in Google Drive.
Create Expense
Create a new expense.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
Create Location
Create a new location.
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
Create Job Title
Create a new job title.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Create User
Create a new user in the brex account.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Create Vendor Card
Create a new vendor card.
Connect any two apps with Notis in the middle.
Google Drive and Brex, 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 Brex.