Review your saved leads with Built In job details
Set a regular time to review saved roles. Notis can retrieve Built In details for leads in your Notion tracker so you can decide what deserves attention.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get job detail
Search and browse tech job listings on Built In to find opportunities that match your skills, then view detailed information about positions including company profiles, salary ranges, benefits, and direct application links. Get job title suggestions to refine your search and discover relevant roles across the tech industry.
Why this helps
Saved leads lose momentum when evaluating them requires reopening many tabs and reconstructing context.
- Creates a regular review point for saved leads.
- Helps gather role and company details for evaluation.
- Makes it easier to decide on a concrete next step.
Setup
Build it in a few focused steps.
- 1Connect Notion and Built In to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to retrieve Built In details on a recurring schedule for leads you track in Notion.
- 3Write one plain-language instruction describing how to identify relevant leads and summarize available listing details.
- 4Choose a recurring trigger and run-report channel, then test using one real saved lead.
Questions about this workflow
Can it review leads I already saved?
Yes. Instruct Notis to use your existing Notion job tracker and identify the leads relevant to the review.
What details are useful in a review?
Built In job details may include company profiles, salary ranges, benefits, and direct application links.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Built In. A trigger fires from one place; an action lands in another.
Notion triggers
Built In actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get job detail
Search and browse tech job listings on Built In to find opportunities that match your skills, then view detailed information about positions including company profiles, salary ranges, benefits, and direct application links. Get job title suggestions to refine your search and discover relevant roles across the tech industry.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Suggest job titles
Search and browse tech job listings on Built In to find opportunities that match your skills, then view detailed information about positions including company profiles, salary ranges, benefits, and direct application links. Get job title suggestions to refine your search and discover relevant roles across the tech industry.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Search tech jobs
Search and browse tech job listings on Built In to find opportunities that match your skills, then view detailed information about positions including company profiles, salary ranges, benefits, and direct application links. Get job title suggestions to refine your search and discover relevant roles across the tech industry.
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 Built In, 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 Built In.