Check investigated network ranges as public issues arrive
Give a newly reported network range an aggregated abuse check at the start of investigation.
Trigger
Public Team Issue Created
Fires when a new issue is created in a Linear *public* team. For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_CREATED`.
Action
Check Block
Tool to check the reputation of all ip addresses in a cidr range. use when you need aggregated abuse data for a network block.
Why this helps
Copying a full network range into another tool adds friction at exactly the point a new lead needs triage.
- Check an entire block when a range is first documented.
- Give investigators aggregated abuse context up front.
- Reduce repeated range lookup steps.
Setup
Build it in a few focused steps.
- 1Connect Linear and Abuselpdb to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to create one in plain language.
- 3Tell Notis to check the CIDR range in a new public investigation issue and summarize aggregated abuse data.
- 4Select the Linear Public Team Issue Created trigger and choose a channel for run reports.
- 5Test with one real public issue containing a relevant CIDR range.
Questions about this workflow
What should a new issue contain?
It should document a CIDR range that the team is authorized to investigate.
How is this different from checking one IP?
A CIDR check examines aggregated abuse data for a network block rather than one individual address.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Abuselpdb. A trigger fires from one place; an action lands in another.
Linear triggers
Abuselpdb actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Retrieve IP Blacklist
Tool to retrieve a list of the most reported ip addresses. use when building dynamic blocklists or threat intelligence feeds.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Bulk Report
Tool to submit multiple ip abuse reports in bulk. use when you need to report a large set of ips at once by uploading a csv file with required headers. csv must include columns: ip, categories, reportdate, comment.
Comment Received Trigger
Triggered when a comment is received.
Check Block
Tool to check the reputation of all ip addresses in a cidr range. use when you need aggregated abuse data for a network block.
Issue Created Trigger
Triggered when a new issue is created.
Check IP Reputation
Tool to check the reputation of an ip address. use when you need to determine if an ip address has been reported for abusive activity within a specified look-back period. example: checkip(ipaddress='8.8.8.8', maxageindays=90).
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Clear Address Reports
Tool to remove all reports associated with a specific ip address. use when you need to purge your own abuse records after verifying control of the 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 Abuse Reports
Tool to retrieve a list of abuse reports for a specific ip address. use when you need to fetch historic reports with optional filtering by status, date range, reporter, and pagination.
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 Abuselpdb, 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 Abuselpdb.