Assess Prospect Email Reputation Automatically
Neurodivergent founders get bogged down in low-quality leads. Stop wasting outreach on spam--score prospect email reputation automatically.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
Email reputation
Tool to enrich an email address with reputation and risk scoring data. use when you need to assess an address's deliverability and risk before outreach. use after confirming your api key is valid.
Why this helps
You waste sales time pitching to spam traps and compromised emails, reducing your actual reach to legitimate prospects.
- Identify spam traps and invalid prospects before wasting outreach
- Score legitimate high-intent prospects automatically
- Improve sales team efficiency by focusing on real opportunities
Setup
Build it in a few focused steps.
- 1Connect your Notion sales pipeline and Abstract account to Notis.
- 2Tell Notis: 'When a prospect's email or information is updated, score their email for reputation and risk so I know who is worth pursuing.'
- 3Set trigger to 'Page Content Updated' on your prospects database.
- 4Select your notification channel for scoring results.
- 5Update a prospect record to test the reputation scoring workflow.
Questions about this workflow
How should I use reputation scores in my sales strategy?
Prioritize high-reputation prospects for immediate outreach, and investigate or deprioritize lower-score prospects until you verify them independently.
What if a good prospect has a low reputation score?
Use the score as context, not a veto--some legitimate prospects may have lower scores due to corporate email patterns; verify through LinkedIn or other channels.
Can I automate follow-up based on reputation scores?
Yes--set up a workflow to tag prospects with high scores for fast-track outreach and low scores for verification before outreach.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Abstract. A trigger fires from one place; an action lands in another.
Notion triggers
Abstract actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Validate IBAN
Tool to validate the format and country code of an iban number. use after collecting an iban to ensure it is correctly formatted.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Email reputation
Tool to enrich an email address with reputation and risk scoring data. use when you need to assess an address's deliverability and risk before outreach. use after confirming your api key is valid.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Email Validation
Tool to validate whether an email address is real and deliverable. use after collecting an email address to confirm deliverability.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
Connect any two apps with Notis in the middle.
Notion and Abstract, 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 Abstract.