Estimate payments for incoming vehicle candidates
Send a candidate request to Notis from a connected tool and get a Carfax estimated payment for review.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Get estimated payment
Access data from carfax.com.
Why this helps
Vehicle candidates captured outside your main workspace can miss the same affordability review as everything else.
- Bring external candidate captures into the same payment review habit.
- Reduce manual handoffs from another tool into vehicle research.
- Get budget context closer to the moment a candidate is shared.
Setup
Build it in a few focused steps.
- 1Connect Notion and Carfax to Notis once through the portal if Notion context is part of your process.
- 2Create the automation in the portal and describe how an incoming vehicle request should lead to a Carfax estimated payment.
- 3Select an incoming webhook as the trigger and have your external tool send a real candidate request to it.
- 4Choose where Notis should report runs, then test with one real request.
Questions about this workflow
Does the webhook come from Notion?
This workflow uses a Notis webhook, so an external tool or custom backend starts it. Use a Notion integration trigger when the Notion event itself should start the workflow.
Is the estimated payment definitive?
No. It is an estimate to support review, not a financing commitment.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Carfax. A trigger fires from one place; an action lands in another.
Notion triggers
Carfax actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Search cars by body type
Access data from carfax.com.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Carfax value
Access data from carfax.com.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Search new car listings
Access data from carfax.com.
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.
Get vehicle reviews
Access data from carfax.com.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get listing detail
Access data from carfax.com.
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 estimated payment
Access data from carfax.com.
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 Carfax, 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 Carfax.