Add past sales to the first review of a vehicle
A review subpage can start with context from earlier auction outcomes. Let Notis retrieve Bid.Cars sales history when the page is added.
Trigger
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Action
Get sales history
Search and browse salvage and insurance vehicle auctions from Copart and IAAI marketplaces, view detailed listing information including photos, pricing history, and vehicle specifications by VIN or lot number. Find similar vehicles, access sales history, and explore available makes and models to discover your next auction opportunity.
Why this helps
Initial reviews can focus on current details while overlooking relevant past auction results.
- Bring past sales into the first review pass.
- Reduce a separate research step for each review.
- Give discussion a stronger starting context.
Setup
Build it in a few focused steps.
- 1Connect Notion and Bid.Cars to Notis once through the portal.
- 2Ask Notis to retrieve sales history for the vehicle on each new review subpage.
- 3Choose Page Added to Page for the review parent and select a channel for run reports.
- 4Add one real review subpage with a VIN or lot number and examine its history.
Questions about this workflow
Does this work for review pages under one parent?
Yes. Page Added to Page watches new subpages directly under the specified parent.
Is past sales history a prediction?
No. It provides available historical auction information to consider during your review.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Bid.Cars. A trigger fires from one place; an action lands in another.
Notion triggers
Bid.Cars actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Look up vehicle by VIN
Search and browse salvage and insurance vehicle auctions from Copart and IAAI marketplaces, view detailed listing information including photos, pricing history, and vehicle specifications by VIN or lot number. Find similar vehicles, access sales history, and explore available makes and models to discover your next auction opportunity.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get sales history
Search and browse salvage and insurance vehicle auctions from Copart and IAAI marketplaces, view detailed listing information including photos, pricing history, and vehicle specifications by VIN or lot number. Find similar vehicles, access sales history, and explore available makes and models to discover your next auction opportunity.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Search auctions by keyword
Search and browse salvage and insurance vehicle auctions from Copart and IAAI marketplaces, view detailed listing information including photos, pricing history, and vehicle specifications by VIN or lot number. Find similar vehicles, access sales history, and explore available makes and models to discover your next auction opportunity.
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.
List makes
Search and browse salvage and insurance vehicle auctions from Copart and IAAI marketplaces, view detailed listing information including photos, pricing history, and vehicle specifications by VIN or lot number. Find similar vehicles, access sales history, and explore available makes and models to discover your next auction opportunity.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get lot photos
Search and browse salvage and insurance vehicle auctions from Copart and IAAI marketplaces, view detailed listing information including photos, pricing history, and vehicle specifications by VIN or lot number. Find similar vehicles, access sales history, and explore available makes and models to discover your next auction opportunity.
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.
Get similar lots
Search and browse salvage and insurance vehicle auctions from Copart and IAAI marketplaces, view detailed listing information including photos, pricing history, and vehicle specifications by VIN or lot number. Find similar vehicles, access sales history, and explore available makes and models to discover your next auction opportunity.
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 Bid.Cars, 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 Bid.Cars.