Add contact context to a verified address request
Keep address checks and contact research together so a useful request does not become another open tab to revisit.
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
Teams often verify delivery or location details, then lose time searching for the person connected to the request.
- Carry verified location context into contact research.
- Ask Crustdata for additional information about the identified person.
- Summarize returned details alongside the request for easier review.
Setup
Build it in a few focused steps.
- 1Connect Addresszen and Crustdata once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Describe the outcome: use the contact identifier and verified location in each request to enrich the person with Crustdata and summarize returned details.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real request containing an Addresszen-verified location and a person identifier.
Questions about this workflow
What person information is needed?
Provide a person identifier and any context needed to distinguish the individual. The enrichment endpoint retrieves additional information based on its query; available results can vary.
Does Addresszen provide contact-created events?
No Addresszen trigger events are listed. An external system needs to send the relevant request to the Notis webhook.
Will this verify the address again?
Addresszen is the source of the verified location in this workflow. Crustdata's selected action enriches a person and does not perform address verification.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Addresszen to Crustdata. A trigger fires from one place; an action lands in another.
Addresszen 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.
Addresszen 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.