Keep private issue IP lookups within the EU endpoint
For private issue investigations that need EU data residency, use Ipdata co's EU-specific lookup when a new issue includes an IP address.
Trigger
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Action
EU-specific IP lookup
Tool to lookup a specific IP address via the EU-only data residency endpoint. Use when you need IP lookup processed and stored within the EU.
Why this helps
A separate lookup can break focus and add uncertainty about where IP data is processed.
- Use the EU-only IP lookup endpoint.
- Get a report when a private issue starts an investigation.
- Reduce context switching during sensitive triage.
Setup
Build it in a few focused steps.
- 1Connect Linear and Ipdata co to Notis once through the portal.
- 2Create a named automation in the portal or ask Notis to create it conversationally.
- 3Use one prompt asking Notis to find an IP in a new private-team issue and look it up with Ipdata co's EU-specific endpoint.
- 4Select the Private Team Issue Created trigger and choose the run-report channel.
- 5Test with an appropriate private issue containing an IP address.
Questions about this workflow
Which lookup action does this use?
It uses Ipdata co's EU-specific IP lookup action for an IP address.
Does the action itself choose which issue content to inspect?
Describe in the prompt that Notis should use the new issue context to find an IP address before running the lookup.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Ipdata co. A trigger fires from one place; an action lands in another.
Linear triggers
Ipdata co actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Advanced ASN Lookup
Tool to perform advanced ASN lookup returning prefixes, peers, and registry details. Use after confirming ASN number when detailed ASN info is required.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Carrier Data for an IP
Tool to return mobile carrier data for a specific IP. Use when you need carrier name, MCC, and MNC for an IP address.
Comment Received Trigger
Triggered when a comment is received.
EU-specific IP lookup
Tool to lookup a specific IP address via the EU-only data residency endpoint. Use when you need IP lookup processed and stored within the EU.
Issue Created Trigger
Triggered when a new issue is created.
IPData: Calling Code
Tool to fetch the international calling_code for an IP's country. Use when you need only the calling code field from ipdata_co.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
IPDATA Field Carrier
Tool to return only the carrier object for the calling IP. Use when you need mobile carrier details of a specific IP.
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).
Get City from IP
Tool to return only city for an IP. Use when only the city name is required.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
IPData: Continent Code
Tool to return only continent_code for an IP. Use when only the continent code is required.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Get Continent Name from IP
Tool to return only continent name for an IP. Use when only the continent name is required.
Connect any two apps with Notis in the middle.
Linear and Ipdata co, 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 Ipdata co.