See Buildkite agent availability when Jira work comes in
A new issue can mean new build work. Get a current view of connected Buildkite agents as soon as it lands in Jira.
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 Pipeline Agents
Tool to list connected agents for an organization. use after confirming the organization slug. supports optional filtering and pagination.
Why this helps
A Jira ticket can signal urgent work, but checking available build agents means another context switch and a follow-up to remember.
- See current connected agent availability alongside new Jira work.
- Reduce manual checks across project tools.
- Route a useful status summary to your chosen report channel.
Setup
Build it in a few focused steps.
- 1Connect Jira and Buildkite once in the Notis portal.
- 2Create an automation in Automations, New Automation, with a name and prompt.
- 3Describe that each new Jira issue should trigger a Buildkite connected-agent check and summarize the result.
- 4Pick Jira New Issue as the trigger and choose where run reports go.
- 5Test with one real Jira issue and confirm the agent snapshot is useful.
Questions about this workflow
Which Jira issues start this automation?
Only issues created in the Jira project configured for the New Issue trigger produce an event.
What will the Buildkite step return?
It lists connected agents for the organization. Confirm the organization slug in your instruction; optional filtering and pagination are supported.
Does this trigger create or start a Buildkite build?
No. The available Buildkite action lists connected agents; it does not trigger builds.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Buildkite. A trigger fires from one place; an action lands in another.
Jira triggers
Buildkite actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Current Access Token
Tool to retrieve the authenticated api access token details. use when you need to confirm the validity and scopes of the current api token.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Meta
Tool to retrieve metadata about the buildkite api. use when you need to fetch webhook ip addresses for firewall or security configurations.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
List Pipeline Agents
Tool to list connected agents for an organization. use after confirming the organization slug. supports optional filtering and pagination.
New Project
Triggered when a new project is added in Jira
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 Buildkite, 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 Buildkite.