Act on access changes before a card is used again
When a monitored Salesforce status signals that card access should end, Notis can deactivate the identified Brex card and report any uncertain match for review.
Trigger
Record Updated (Generic SObject)
Triggers when monitored fields change on any Salesforce SObject. You specify the SObject type and which field values should be returned in the payload. The trigger uses SystemModstamp to detect changes regardless of which specific field changed.
Action
Update Card Status
Update the status of a card (activate/deactivate/terminate).
Why this helps
An access change in CRM may not reach the card administrator before another purchase occurs.
- Connect a defined status change to a timely card action.
- Reduce manual handoffs for card access changes.
- Report uncertain card matches instead of acting on the wrong card.
Setup
Build it in a few focused steps.
- 1Connect Salesforce and Brex once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In one instruction, define the monitored record type and status change that requires deactivation and how to identify the card safely.
- 4Pick Record Updated (Generic SObject) as the trigger, specify the SObject type and returned fields, and choose where run reports should go.
- 5Test with one real status update and confirm the intended card is deactivated.
Questions about this workflow
What does the generic Salesforce trigger require?
You specify the SObject type and which field values should be returned. It detects changes using SystemModstamp, so include the status and identifiers needed for your rule.
Can the trigger itself decide who is leaving?
The event reports record changes. Your instruction must define which change means card access should end and how to identify the right Brex card.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Salesforce to Brex. A trigger fires from one place; an action lands in another.
Salesforce 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.
Account Created or Updated
Triggers when an Account is created or updated in Salesforce. Uses LastModifiedDate high-watermark to capture both creations and updates.
Create Department
Create a new department.
Contact Updated
Triggers when an existing Salesforce Contact record is modified. Emits changed fields alongside relevant timestamps.
Create Expense
Create a new expense.
Record Updated (Generic SObject)
Triggers when monitored fields change on any Salesforce SObject. You specify the SObject type and which field values should be returned in the payload. The trigger uses SystemModstamp to detect changes regardless of which specific field changed.
Create Location
Create a new location.
New Contact Trigger
Triggers when a new Contact is Created in Salesforce.
Create Job Title
Create a new job title.
New Lead Trigger
Triggers when a new Lead is created in Salesforce.
Create User
Create a new user in the brex account.
New or Updated Opportunity
Triggers when a Salesforce Opportunity is created or updated.
Create Vendor Card
Create a new vendor card.
Connect any two apps with Notis in the middle.
Salesforce 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.