Check vendor context while handling Jira purchase work
Bring the supplier directory into the request so you can make the next decision with fewer searches.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
List Vendors
List all vendors.
Why this helps
Purchase requests often stall while someone checks whether a supplier is already in the spend system.
- Surface vendor directory context during request review.
- Reduce duplicate supplier searches across tools.
- Use supplied criteria to summarize relevant vendor results.
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 vendor review.
- 3Tell Notis in one instruction which purchase requests qualify and what vendor details or matching criteria to use.
- 4Pick Jira New Issue and select a report destination.
- 5Test with a real purchase request and review the vendor results.
Questions about this workflow
Does this create a vendor or card?
No. It retrieves the existing Brex vendor list. Vendor card creation is a separate action.
Can it determine if a vendor is already present?
It can compare the returned vendor information with the requested name when the issue or instruction provides a reliable name.
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.