Look up codes in your maintenance notes
Add a diagnostic code to your maintenance page and let Notis retrieve the reference while you are already documenting the issue.
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
Look up OBD-II code
Search vehicle ratings, OBD-II diagnostic codes, and current lease deals across years, makes, and models from Kelley Blue Book. Get comprehensive car information and pricing data to compare vehicles and find the best deals.
Why this helps
Maintenance notes can accumulate codes without a clear next step, creating another item to remember after the current task.
- Pair documenting a code with a reference lookup.
- Reduce the chance that a maintenance note remains unexplained.
- Keep the issue and its research context close together.
Setup
Build it in a few focused steps.
- 1Connect Notion and Kelley Blue Book to Notis once in the portal.
- 2Create an automation prompt asking Notis to look up any OBD-II code added to the maintenance note.
- 3Select Page Content Updated and scope it to the maintenance page or data source; choose a run-report channel.
- 4Test by adding one real code to the note and review the returned information.
Questions about this workflow
Will this inspect the car?
No. It retrieves reference information for a code; it does not perform a physical inspection or determine the repair.
Can I scope it to one maintenance page?
Yes. Page Content Updated can be scoped to a single page or data source.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Kelley Blue Book. A trigger fires from one place; an action lands in another.
Notion triggers
Kelley Blue Book actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List model years
Search vehicle ratings, OBD-II diagnostic codes, and current lease deals across years, makes, and models from Kelley Blue Book. Get comprehensive car information and pricing data to compare vehicles and find the best deals.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get car ratings
Search vehicle ratings, OBD-II diagnostic codes, and current lease deals across years, makes, and models from Kelley Blue Book. Get comprehensive car information and pricing data to compare vehicles and find the best deals.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List models
Search vehicle ratings, OBD-II diagnostic codes, and current lease deals across years, makes, and models from Kelley Blue Book. Get comprehensive car information and pricing data to compare vehicles and find the best deals.
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 vehicle ratings, OBD-II diagnostic codes, and current lease deals across years, makes, and models from Kelley Blue Book. Get comprehensive car information and pricing data to compare vehicles and find the best deals.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Look up OBD-II code
Search vehicle ratings, OBD-II diagnostic codes, and current lease deals across years, makes, and models from Kelley Blue Book. Get comprehensive car information and pricing data to compare vehicles and find the best deals.
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 Kelley Blue Book, 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 Kelley Blue Book.