Check Buildkite API access when a Jira issue changes
Keep an eye on whether your Buildkite connection can do its job. A Jira issue update can trigger a quick token validity and scope check.
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
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.
Why this helps
When access problems surface during delivery, it is easy to lose time finding the token details and checking the connection manually.
- Retrieve authenticated token details when Jira work changes.
- Review token validity and scopes without opening another console.
- Send the result to a consistent run report destination.
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.
- 3Tell Notis to retrieve Buildkite token details and summarize validity and scopes after a Jira issue update.
- 4Pick Jira Updated Issue as the trigger and choose where run reports go.
- 5Test with one real issue update and review the access summary.
Questions about this workflow
Does every Jira update trigger the check?
Updates to existing issues in the configured Jira project trigger the event. Comment activity does not.
Does this automation change token permissions?
No. It retrieves authenticated API token details so you can confirm validity and scopes.
Can I use it to test Buildkite connectivity?
It can retrieve the current token details. The result can help you review whether the token is valid and has expected scopes.
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.