Add useful contact context to abuse reports
Send a report with a contact you already know, and get a richer person profile ready for your review.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Enrich person screener
Enriches a person’s profile with additional information.
Why this helps
Abuse reports can arrive with a contact name but little context, leaving you to research who they are before deciding what to do.
- Enriches a person named in an incoming report using the details supplied with the request.
- Keeps incident context and contact research together in a run report.
- Helps you decide on follow-up without switching between tools to research the contact.
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 use the report details and supplied contact identifiers to enrich that person in Crustdata, then summarize the result.
- 4Choose the webhook trigger and where run reports should go.
- 5Send one real example containing an abuse report and a known contact to test the workflow.
Questions about this workflow
Does Abuselpdb trigger this workflow directly?
No. Abuselpdb has no listed trigger events. A webhook starts the workflow when an external tool or backend sends the request.
What contact information should the webhook include?
Include the person details you have, such as a name and company or other identifiers your process can supply. The person enrichment action uses the query Notis prepares from that information.
Does this workflow decide how to respond to the abuse report?
No. It enriches the named person and summarizes the result for review. Your team decides what follow-up is appropriate.
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.