Get a current headcount when a company enters your pipeline
Let Clay look up employee count as soon as a company lands in your Notion prospect database, without stopping to research it by hand.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Get Company Employee Count
Get a company's current employee headcount from its domain.
Why this helps
Guessing company size or postponing the lookup makes qualification feel like another task to remember.
- Request a current employee count from the company's domain.
- Make company qualification easier to pick up later.
- Avoid opening a separate research workflow for each new prospect.
Setup
Build it in a few focused steps.
- 1Connect Notion and Clay to Notis once through the portal.
- 2Tell Notis to use the company domain on each new prospect record to ask Clay for the current employee count.
- 3Choose the Notion New Page trigger for the prospect database and choose where run reports should go.
- 4Test with one real prospect record that has a company domain.
Questions about this workflow
What does Clay use to look up headcount?
The selected Clay action retrieves a company's current employee count from its domain.
Can I use this for every new prospect in a database?
Yes. Choose the New Page trigger scoped to that Notion database.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Clay. A trigger fires from one place; an action lands in another.
Notion triggers
Clay actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Find Mobile Phone
Find a person's mobile phone number from their LinkedIn URL, name, and company.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Company Employee Count
Get a company's current employee headcount from its domain.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Advanced Search
Start an advanced-query search for people or companies and get a search_id.
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.
Find Company Domain from Name
Resolve a company name to its primary website domain.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Search Query Reference
Fetch the query-language reference for authoring advanced people/company searches.
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.
Fetch Advanced Search Results
Fetch the next page of results for an advanced search by search_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 Clay, 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 Clay.