Deactivate Cards Immediately on Security Issues
When security incidents occur, deactivate cards instantly from Linear. No manual Brex steps during emergencies.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Action
Update Card Status
Update the status of a card (activate/deactivate/terminate).
Why this helps
Security incidents require fast card deactivation, but manual Brex steps waste critical response time
- Instant card deactivation
- Faster security response
- Reduced fraud exposure
- Emergency action in seconds
Setup
Build it in a few focused steps.
- 1Connect Linear and Brex integrations to Notis.
- 2Create an automation called 'Emergency Card Deactivation' with this prompt: 'When a Linear issue is labeled card-deactivation, immediately deactivate the card identified in the issue and send a confirmation message.'
- 3Select 'Issue Updated' as your trigger and filter for the card-deactivation label.
- 4Choose a high-priority notification channel for deactivation confirmations.
- 5Test by creating a Linear issue labeled card-deactivation and updating it to trigger deactivation.
Questions about this workflow
How does Notis know which card to deactivate?
Include the cardholder name or card last 4 digits in the Linear issue. Notis will identify and deactivate that card.
Can I reactivate a card after deactivation?
Yes, reactivation needs manual Brex action or a separate workflow to prevent accidental reactivations.
What if there's a false alarm?
If deactivated by mistake, you can manually reactivate in Brex immediately or update the Linear issue to trigger reactivation.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Brex. A trigger fires from one place; an action lands in another.
Linear 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 Received Trigger
Triggered when a comment is received.
Create Department
Create a new department.
Issue Created Trigger
Triggered when a new issue is created.
Create Expense
Create a new expense.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Create Location
Create a new location.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Create Job Title
Create a new job title.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Create User
Create a new user in the brex account.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Create Vendor Card
Create a new vendor card.
Connect any two apps with Notis in the middle.
Linear 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.