Pull abuse report history from the issue conversation
Ask for an IP's report history in the Linear discussion and get the findings where the team is already working.
Trigger
Comment Received Trigger
Triggered when a comment is received.
Action
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.
Why this helps
Investigation requests can get buried when someone has to leave the discussion, find the IP, and look up its report history separately.
- Turn a clear comment request into a report-history lookup.
- Keep findings close to the investigation discussion.
- Cut down on repeated searches across tools.
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 make one.
- 3Tell Notis to fetch abuse reports for an IP when a Linear comment explicitly requests its history, then summarize relevant results.
- 4Select the Linear Comment Received trigger and choose a channel for run reports.
- 5Test with one real comment that names an IP and requests its report history.
Questions about this workflow
Does the comment need to name the IP?
Yes. The request should identify the specific address whose abuse reports Notis should fetch.
Can results be filtered?
The prompt can ask Notis to apply relevant supported filters, such as status or date range, when the request provides them.
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.