Get Webhook IPs for Private Network Setup
Private teams need webhook IPs for firewall configuration. Get them automatically without leaving Linear.
Trigger
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
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
Private team setting up integration behind firewall, needs webhook IPs but documentation is hard to find - security-sensitive projects have extra complexity
- Webhook IPs fetched automatically for private teams
- Firewall setup completed without friction
- Private network security maintained with accurate ranges
- No manual documentation hunting for sensitive projects
Setup
Build it in a few focused steps.
- 1Connect Linear and Buildkite to Notis
- 2Create automation: When an issue is created in a private Linear team about webhook or firewall configuration, fetch the Buildkite webhook IP metadata
- 3Select Private Team Issue Created as the trigger
- 4Set your notification channel
- 5Test by creating an issue in a private team and confirm webhook IPs appear
Questions about this workflow
Are these the same IPs as the public webhook automation?
Yes - webhook IPs are identical regardless of team privacy. This automation applies to private team workflows.
Can I restrict this to specific private teams?
You can filter by team name, or create separate automations for different private teams if needed
Do private teams need different webhook configuration?
IPs are the same. Private team setup may need additional security steps depending on your network architecture.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Buildkite. A trigger fires from one place; an action lands in another.
Linear 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.
Comment Received Trigger
Triggered when a comment is received.
List Pipeline Agents
Tool to list connected agents for an organization. use after confirming the organization slug. supports optional filtering and pagination.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear 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.