Align card limits with changing Jira work
When the work changes, make the card control update part of the same follow-through.
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 Limits
Update spending limits and controls for a card.
Why this helps
A changed project need can leave a card limit too high or too low until someone notices and acts.
- Prompt a timely review of card controls after scope changes.
- Keep the Jira change connected to the resulting Brex limit update.
- Require explicit card identity and limit values or a defined source.
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 card limit workflow.
- 3Describe in one instruction which issue changes affect card limits and provide the Brex card reference and new limit rules.
- 4Pick the Jira Updated Issue trigger and select a report destination.
- 5Test with one real qualifying issue update and inspect the resulting card limits.
Questions about this workflow
Can Notis know which card belongs to an issue?
No relationship is specified by the trigger descriptions. Provide a card identifier or a reliable way to obtain it in your instruction.
Do Jira comments trigger a limit review?
No. The Updated Issue event excludes 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.