Bring Breeze Project Details into Jira Requests
Give internal request flows a direct way to fetch the Breeze context needed for project decisions.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get Project
Tool to get a specific project by id. use when you need detailed project information after confirming the project id. example: "get project 123 details".
Why this helps
Teams can lose time looking up project details manually while working through a Jira request.
- Retrieve detailed information for a specified Breeze project.
- Reduce manual project lookups during request handling.
- Make context available in the report channel.
Setup
Build it in a few focused steps.
- 1Connect Jira and Breeze once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis in plain language from any channel.
- 3Specify the Breeze project id supplied in the incoming request and ask Notis to summarize its details.
- 4Pick a Notis webhook trigger and choose where run reports should go.
- 5Test with one real request and verify the intended project's details.
Questions about this workflow
Does the request need to include a Breeze project id?
Yes, unless another supported source supplies the id. Get Project requires a valid project id.
Can it update project details?
No. The Get Project action retrieves project information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Breeze. A trigger fires from one place; an action lands in another.
Jira triggers
Breeze actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Project People
Tool to add people to a project. use when you have a valid project id and one or more email addresses to invite them.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Archive Project
Tool to archive a specific project. use when you need to hide a completed or inactive project from active views after confirming its details.
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 Card
Tool to create a new card in a project. use after confirming the project id. creates a task with details like name, due date, and assignees.
New Project
Triggered when a new project is added in Jira
CREATE_LIST
Tool to create a new list (stage) in a breeze project. use when you've selected a project and need to add a new stage. example: "create a new todo list for project 42."
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 Project
Tool to create a new project in breeze. use when you have the project name and want to initialize it via the api.
Create Workspace
Tool to create a new workspace. use after deciding on the workspace name.
Delete Card
Tool to delete a specific card (task) by its id. use when you need to remove a task permanently; deletions cannot be undone.
Delete Project
Tool to delete a specific project by id. use when you need to remove a project after confirming its id.
Connect any two apps with Notis in the middle.
Jira and Breeze, 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 Breeze.