Keep Brex user details current with Jira changes
Make role and organization updates easier to carry through after the Jira request changes.
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 User
Update user details.
Why this helps
A role change can be recorded in Jira while user details in Brex remain stale and require a separate reminder.
- Prompt consistent follow-through on user changes.
- Keep the request context connected to the Brex update.
- Require a clear user match and the precise details to change.
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 it for user detail updates.
- 3Describe in one instruction which changes qualify, how to identify the Brex user, and what new values to apply.
- 4Pick Jira Updated Issue and choose where reports should go.
- 5Test with one real role change issue update and review the Brex user.
Questions about this workflow
Can the automation identify the user from Jira alone?
Only if the issue provides a reliable identity that can be matched to a Brex user. Include the matching rule or another source in your instruction.
Will comments trigger the update?
No. Jira Updated Issue does not fire for comment activity.
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.