Follow through on card status changes from Jira
Make a card status action part of the access update that prompted it.
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 Card Status
Update the status of a card (activate/deactivate/terminate).
Why this helps
Cards can remain active after access needs change because the status update is handled in a different workflow.
- Keep card status follow-through tied to access work.
- Reduce the chance of a status change being forgotten.
- Make card identity and intended status explicit.
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 card status follow-through.
- 3Describe which Jira updates qualify, how to identify the card, and which status to apply.
- 4Pick Jira Updated Issue and select a run report destination.
- 5Test with one real access update and verify the Brex card status.
Questions about this workflow
Can this infer the correct card status?
Your instruction should define the condition and intended status. The Jira event description does not provide an access policy.
Do comment changes start it?
No. The Updated Issue event 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.