Keep Brex budgets aligned with Jira changes
When project scope shifts, turn the Jira update into a clear budget maintenance step.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Action
Update Budget
Update budget details.
Why this helps
A changed Jira issue can leave the spend plan out of date while the team assumes someone else will update it.
- Create a prompt-driven reminder to keep project budgets current.
- Reduce manual follow-up after meaningful Jira changes.
- Use supplied budget identifiers and revised values rather than guessing.
Setup
Build it in a few focused steps.
- 1Connect Jira and Brex once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name the budget update workflow.
- 3Describe in one instruction which Jira changes matter and how to update the identified Brex budget; include the budget identifier and the revised details or their source.
- 4Pick the Jira Updated Issue trigger and choose a report channel.
- 5Test with one real changed issue and review the Brex budget update.
Questions about this workflow
Can Notis infer which Brex budget matches an issue?
The available event descriptions do not provide a built-in issue-to-budget relationship. Include a stable budget identifier or explicit matching rule and data source in your instruction.
Does this trigger run for Jira comments?
No. Updated Issue does not fire on comment activity such as adding, editing, or deleting a comment.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Brex. A trigger fires from one place; an action lands in another.
Jira 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.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Create Department
Create a new department.
New Project
Triggered when a new project is added in Jira
Create Expense
Create a new expense.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Create Location
Create a new location.
Create Job Title
Create a new job title.
Create User
Create a new user in the brex account.
Create Vendor Card
Create a new vendor card.
Connect any two apps with Notis in the middle.
Jira 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.