Isolate Travel Spending in Transaction Reports
When team members report travel expenses in Linear, pull just the travel-related transactions from Brex automatically.
Trigger
Issue Created Trigger
Triggered when a new issue is created.
Action
Get Card Transactions
Get card transactions for a date range.
Why this helps
Separating travel expenses from operational spending requires manual filtering and context-switching between systems
- Travel spending isolated automatically
- Easier expense categorization
- Faster reimbursement processing
- Clear travel cost visibility
Setup
Build it in a few focused steps.
- 1Connect Linear and Brex integrations to Notis.
- 2Create an automation called 'Travel Expense Report' with the prompt: 'When a Linear issue is labeled travel-expense, get all Brex card transactions from the travel date range mentioned in the issue.'
- 3Select 'Issue Created' as your trigger and filter for the travel-expense label.
- 4Choose your notification channel for travel expense summaries.
- 5Test by creating a Linear issue labeled travel-expense with travel dates and verify transactions are retrieved.
Questions about this workflow
How does Notis know which dates to use?
Include travel dates in your Linear issue description (e.g., 'Sept 15-17 conference'). Notis will extract and use those dates.
Can this include hotel and meals?
Yes, if they were charged to the company card. Non-card expenses won't appear, but you can reference receipts in the Linear issue.
What if multiple team members traveled?
Create separate Linear issues for each traveler or team member, and each will trigger its own transaction report.
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.