Check phone availability from an updated prospect record
When prospect details change in Notion, let ContactOut check whether a phone number is available for the LinkedIn profile.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Check Phone Availability
Check whether a phone number exists for a LinkedIn profile; consumes no credits.
Why this helps
Teams can spend time arranging outreach only to discover late that the preferred contact channel is unavailable.
- See whether a phone number exists before planning a call.
- Avoid repeated manual checks while updating prospect records.
- Make contact-channel decisions with less back-and-forth.
Setup
Build it in a few focused steps.
- 1Connect Notion and ContactOut to Notis once through the portal.
- 2Create the automation in the portal or ask Notis for it in plain language.
- 3In one instruction, ask Notis to check phone availability when a prospect's LinkedIn details are updated.
- 4Pick the Notion Page Properties Updated trigger, choose a run-report channel, and test with one real profile.
Questions about this workflow
Does checking phone availability consume credits?
The ContactOut phone availability check consumes no credits.
What identifies the profile to check?
The workflow needs the person's LinkedIn profile URL in the Notion context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to ContactOut. A trigger fires from one place; an action lands in another.
Notion triggers
ContactOut actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
LinkedIn Contacts Only (Work Email)
Contacts only, no profile body, from a LinkedIn URL; bills work email credits.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Check Phone Availability
Check whether a phone number exists for a LinkedIn profile; consumes no credits.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Verify Email
Check one email address's deliverability; a definitive verdict bills one verifier credit.
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.
Enrich Person (Personal Email)
Match a person by any identifier mix; contact reveal bills personal email credits.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
LinkedIn Full Profile + Contacts (Work Email)
Full LinkedIn profile plus contacts from a profile URL; bills work email credits.
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.
Search Companies
Find companies by size, industry, location, revenue, technologies; bills search credits.
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 ContactOut, 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 ContactOut.