Check suspicious IPs from new Jira issues
When a new Jira issue reports an IP address, have Notis check its Abuselpdb reputation and return the result for a quick decision.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
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).
Why this helps
You have to leave Jira, look up each reported IP, then bring the context back before triage can continue.
- Review reported IPs without switching tools.
- See the reputation result alongside the issue context.
- Reduce manual lookups during issue triage.
Setup
Build it in a few focused steps.
- 1Connect Jira and Abuselpdb once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis from any channel.
- 3In one instruction, ask Notis to find an IP in each new issue, check its reputation, and summarize the result.
- 4Pick the Jira New Issue trigger and choose where run reports should go.
- 5Test with one real issue that contains an IP address.
Questions about this workflow
Which Jira issues start this workflow?
It runs for issues created in the Jira project configured for the New Issue trigger.
Does it file an abuse report?
No. It checks the IP reputation and summarizes the result; it does not submit a report.
What if the issue has no IP address?
Notis can report that no IP was found. The trigger does not provide an IP-specific filter.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Abuselpdb. A trigger fires from one place; an action lands in another.
Jira 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.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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.
New Project
Triggered when a new project is added in Jira
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).
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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.
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.
Connect any two apps with Notis in the middle.
Jira 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.