Review threat signals without leaving the conversation
A comment can contain the one detail that changes an investigation. Check its IP for threat indicators and keep the findings close to the Linear discussion.
Trigger
Comment Received Trigger
Triggered when a comment is received.
Action
IPData Threat for IP
Tool to return threat intelligence data for a specific IP. Use when you need to determine if an IP is a Tor node, VPN, proxy, datacenter, threat actor, or listed on blocklists.
Why this helps
Threat checks buried in comments are easy to postpone when they require opening another tool and repeating the address.
- Check for VPN, proxy, Tor, datacenter, and blocklist signals.
- Keep the finding connected to the comment that prompted it.
- Avoid a separate manual threat lookup.
Setup
Build it in a few focused steps.
- 1Connect Linear and Ipdata co to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally to create one.
- 3Use a single prompt asking Notis to find IP addresses in new comments, check each with Ipdata co threat intelligence, and report the indicators.
- 4Select the Linear Comment Received trigger and choose where run reports should arrive.
- 5Test with a real comment containing an IP address.
Questions about this workflow
Does this decide whether an IP is malicious?
No. It reports Ipdata co threat signals so a person can review them in context.
Can it ignore comments without an IP?
Yes. Include that instruction in the plain-language prompt.
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.