Find company context for an abuse report
Start with a company identifier already in the report and get a Crustdata company screening result to review alongside it.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Screener company information
Finds companies matching criteria such as headcount, growth, or funding.
Why this helps
When a report mentions a company, finding basic company context can add another research task to an already busy incident review.
- Uses a supplied company name or identifier to screen company information in Crustdata.
- Returns a concise company context summary alongside the original report details.
- Makes it easier to triage reports that already name a company.
Setup
Build it in a few focused steps.
- 1Connect Abuselpdb and Crustdata once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3In one instruction, ask Notis to screen the company identified in the incoming report and summarize the matching company context.
- 4Choose the webhook trigger and where run reports should go.
- 5Send one real example with an abuse report and a known company identifier to test the workflow.
Questions about this workflow
Can this identify a company from an IP address alone?
The listed company screener searches company information. The workflow should receive a company name or identifier; no IP-to-company lookup is specified by the available actions.
What does the workflow do with the screening result?
It summarizes the returned company information for review with the report. It does not file an abuse report or take a security action.
Can I start it from Abuselpdb itself?
Abuselpdb has no listed trigger events. An external system or backend must send the report and company identifier to the Notis webhook.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Abuselpdb to Crustdata. A trigger fires from one place; an action lands in another.
Abuselpdb triggers
Crustdata actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Enrich person screener
Enriches a person’s profile with additional information.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Fetch headcount by facet timeseries
Retrieves headcount data over time, grouped by selected facets.
Fetch investor portfolio data
Finds companies whose investor list includes a specified investor and returns funding summaries.
Filter decision makers data
Filters and retrieves decision-maker data across organizations.
Post funding milestone timeseries data
Retrieves time-based data about company funding milestones.
Post headcount timeseries data
Retrieves historical headcount data to help analyze workforce trends.
Post job listings table data
Searches indexed job listings.
Post web traffic data
Retrieves web traffic data for analysis and reporting.
Connect any two apps with Notis in the middle.
Abuselpdb and Crustdata, 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 Crustdata.