Review Bonsai Space Metadata Alongside Jira Issue Updates
When a Jira issue changes, have Notis retrieve the metadata for a named Bonsai space and bring the result into its report.
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
Retrieve Space Details
Tool to retrieve details for a single space by its path. use when you need metadata for a space before provisioning a cluster. use after confirming this detail exists. e.g., 'omc/bonsai/us-east-1/common'.
Why this helps
Issue updates can lose momentum when someone has to leave Jira and look up the related space metadata by hand.
- Bring retrieved space metadata into the issue update report.
- Reduce context switching when reviewing changes.
- Use a space path to retrieve details for the intended Bonsai space.
Setup
Build it in a few focused steps.
- 1Connect Jira and Bonsai once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to retrieve details for the relevant Bonsai space and summarize its metadata with the issue update.
- 4Pick the Jira Updated Issue trigger for the project you configure, then choose where run reports go.
- 5Test with one real issue update and a valid Bonsai space path.
Questions about this workflow
What changes trigger this workflow?
An existing issue changing in the configured Jira project starts it. Comment activity does not trigger this event.
What does the Bonsai action need?
Retrieve Space Details looks up a single space by its path. Provide the relevant path in the instruction or issue context.
Does this provision a cluster?
No. This action retrieves metadata for a space; it does not provision or change infrastructure.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Bonsai. A trigger fires from one place; an action lands in another.
Jira triggers
Bonsai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Bonsai Cluster Details
Tool to retrieve details for a single bonsai cluster by slug. use when you need to inspect a cluster's configuration and status.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Bonsai Spaces
Tool to retrieve a list of all available spaces. use when you need to see the server groups and geographic regions available to your account.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Retrieve Space Details
Tool to retrieve details for a single space by its path. use when you need metadata for a space before provisioning a cluster. use after confirming this detail exists. e.g., 'omc/bonsai/us-east-1/common'.
New Project
Triggered when a new project is added in Jira
List Spaces
Tool to retrieve a list of all available spaces. use when you need to see the server groups and geographic regions available for your account.
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.
Connect any two apps with Notis in the middle.
Jira and Bonsai, 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 Bonsai.