Get Buildkite API metadata when a Jira project is created
A new project often brings setup chores. Put Buildkite API metadata in the run report so useful security details are close at hand.
Trigger
New Project
Triggered when a new project is added in Jira
Action
Get Meta
Tool to retrieve metadata about the buildkite api. use when you need to fetch webhook ip addresses for firewall or security configurations.
Why this helps
Project setup details can get scattered, and finding Buildkite webhook IP addresses later can slow down firewall and security configuration.
- Retrieve Buildkite API metadata when a Jira project is added.
- Keep webhook IP address information close to project setup activity.
- Reduce the chance of a security configuration follow-up being forgotten.
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.
- 3In one instruction, ask Notis to fetch Buildkite API metadata and summarize relevant setup details when a Jira project is added.
- 4Pick Jira New Project as the trigger and choose where run reports go.
- 5Test with one real project event and confirm the metadata summary is actionable.
Questions about this workflow
What information is available from this Buildkite action?
It retrieves Buildkite API metadata. The tool can be used to fetch webhook IP addresses for firewall or security configurations.
Does creating a Jira project configure Buildkite security automatically?
No. Notis can retrieve and report the metadata; your team uses that information to make any needed configuration changes.
Does this trigger run for Jira issue creation?
No. It starts when a new Jira project is added.
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.