Look up codes as troubleshooting notes evolve
Keep your troubleshooting page moving: when you update it with a code, have Notis retrieve its Kelley Blue Book reference.
Trigger
Page Updated
Triggers when any block within a specified Notion page is updated.
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
Troubleshooting often pauses when a code is written down but its meaning or next research step is still unclear.
- Tie the lookup to progress in your troubleshooting notes.
- Keep code research attached to the specific vehicle issue.
- Make the next research step easier to pick up later.
Setup
Build it in a few focused steps.
- 1Connect Notion and Kelley Blue Book to Notis once in the portal.
- 2Create an automation prompt to look up an OBD-II code mentioned in an updated troubleshooting page.
- 3Select Page Updated for the chosen page and choose where run reports should be delivered.
- 4Test with one real page update that includes a code and check the lookup response.
Questions about this workflow
What does Page Updated monitor?
It triggers when a block within the specified Notion page is updated.
Can the prompt avoid lookups on unrelated edits?
Ask Notis to proceed only when the updated content includes an OBD-II code.
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.