# How to Get Car Listing Data in n8n

> Search US dealer listings in n8n by make, model, year, price and mileage with the Auto.dev community node. Three workflows, their real outputs, and the plan each one needs.

2026-11-17 · Auto.dev Team · 6 min read

## In short

Install the n8n-nodes-autodev community node, add an Auto.dev API key, and use the Listing: Get Many operation to search US dealer listings by make, model, year, price, mileage and location. Listings, VIN decoding and photos are on the Free plan. The node also has a trigger for new listings and works as a tool for n8n's AI Agent.

We published an n8n community node for the Auto.dev API in November 2026. This guide shows how to pull dealer listings with it, then three workflows built on top. Every output below comes from a run on 16 or 17 November 2026, on n8n 2.47.7 with version 0.1.0 of the node.

## What you need

- A self-hosted n8n, version 2.46.1 or later. n8n Cloud runs community nodes once n8n has verified them, and this one is in that review now.
- An Auto.dev API key. Create one in your [dashboard](https://www.auto.dev/dashboard/api-keys).

## How to get car listing data in n8n

1. In n8n, open Settings, then Community Nodes, and install `n8n-nodes-autodev`.
2. Add the Auto.dev node to a workflow and choose the Listing resource with the Get Many operation.
3. Create an Auto.dev API credential and paste your key. n8n tests the key when you save it.
4. Under Filters, add what you are searching for, such as Make `Toyota`, Model `Tacoma`, ZIP Code `33132` and Distance `50`.
5. Set Limit to the number of listings you want, then run the node.

Each listing comes out as its own item, so the next node in the workflow runs once per car.

## What a listing looks like

This is one item from that exact search, with Limit set to 3:

```json
{
  "vin": "5TFAZ5CN2HX040274",
  "year": 2017,
  "make": "Toyota",
  "model": "Tacoma",
  "trim": "TRD Off Road",
  "price": 14350,
  "miles": 182691,
  "dealer": "America Auto Wholesale",
  "state": "FL",
  "url": "https://www.americanautomiami.com/details/used-2017-toyota-tacoma/133370989"
}
```

Those ten fields are what the node returns with Simplify switched on, which is the default. Switch it off to get the full response described in the [Vehicle Listings docs](https://docs.auto.dev/v2/products/vehicle-listings).

Listings come from physical and online dealers in the United States. A search is one API request, whatever the number of filters.

## The filters

| Filter | How to write it |
| --- | --- |
| Make, Model, Trim | One value, or several with commas: `Ford,Chevrolet` |
| Body Style, Fuel, Transmission | One value, or several with commas |
| Year, Price, Mileage | A single value or a range: `2019-2023`, `20000-35000` |
| Condition | New or Used |
| Certified Pre-Owned | On or off |
| State | Two-letter code |
| ZIP Code and Distance | A ZIP code and a radius in miles, used together |
| Dealer ID | One dealer's inventory |

Under Options you can also sort by price, mileage, year or listing date, and ask for a later page.

## How do I get an alert when a car I want is listed?

Use the Auto.dev Trigger node. It runs the same search on a schedule and passes on only the listings it has not seen before. Its first check records what is already for sale and sends nothing, so alerts begin with cars listed after you switch the workflow on.

Our market alert workflow adds one step. When something new appears, it fetches the similar cars for sale, averages their prices, and tells you where the new one sits. This message came from a search for a 2019 to 2023 Tacoma, $20,000 to $35,000, under 80,000 miles, within 100 miles of Miami:

```text
New listing: 2023 Toyota Tacoma TRD Off Road
Price: $27990 | Mileage: 7727
Market: $2711 below the average of 20 similar listings ($30701)
Dealer: Auto Benz USA, FL
VIN: 3TMAZ5CN3PM207049
```

It runs on the Free plan. A check is one request, and the comparison is one more when there is something new. The Free plan returns at most 20 listings per request, which is why the average covers 20 cars.

The plan's 1,000 calls a month decide how often you can check. Hourly is about 720 checks a month, and that goes over the limit if most checks find a new car. Every two hours stays under it in every case.

## How do I calculate a car payment in n8n?

The Finance resource has four operations: Get Payments, Get Interest Rates, Get Taxes and Fees, and Get Ownership Cost. Each takes a VIN.

Our deal sheet workflow puts a form in front of three of them. For the Tacoma above at its asking price, with ZIP code 33132, $3,000 down and a 720 credit score, it returned:

| Line | Result |
| --- | --- |
| Vehicle | 2023 Toyota Tacoma 2WD |
| Monthly payment with taxes | $474.50 (72 months at 7.663%) |
| Loan amount | $27,318.40 |
| Taxes and fees | $2,128.40 |
| Rates by term | 36 and 48 months 7.644%, 60 months 7.524%, 72 months 7.663%, 84 months 8.263% |
| Five-year cost to own | $47,167, or $0.63 per mile |

That is four requests: the VIN decode, plus payments, rates and ownership cost, which need the Growth plan.

Ownership cost is not available for every vehicle. A 2003 Honda Accord got a payment and rates but no five-year figure, so the workflow prints "not available for this vehicle" on that line and still shows the rest. These numbers are estimates for quoting, not a lender's offer.

## How do I look up a car from a license plate in n8n?

Use the Plate resource with the Get VIN operation. Give it a state and a plate, and it returns the VIN with the year, make and model. Both it and Get Open Recalls need the Scale plan.

Our check-in workflow is built for a service desk. An advisor types the plate, and the workflow shows that vehicle's unrepaired safety recalls before the customer hands over the keys. It has three outcomes, and we ran each one:

- An open recall. The 2023 Tacoma had one, NHTSA campaign 24V152000 for the rear axle assembly. The advisor sees the component and the remedy text, with a warning in front if the manufacturer says not to drive the vehicle or to park it outside.
- No open recalls. A 2017 Honda Accord had three recalls issued and none open.
- Plate not found. The sample plate in our docs is not a real one, and the workflow told the advisor to check the plate or use the VIN.

We ran the two recall outcomes by giving the workflow the VIN directly, because we did not have a real plate to publish.

## What each plan covers in the node

| Plan | Operations |
| --- | --- |
| Free | VIN: Decode. Listing: Get Many, Get, Get Photos. The New Listing trigger |
| Growth | Everything on Free, plus VIN: Get Specifications, Get Recalls, Get Build Data. Finance: Get Payments, Get Interest Rates, Get Ownership Cost |
| Scale | Everything on Growth, plus VIN: Get Open Recalls. Plate: Get VIN. Finance: Get Taxes and Fees |

Current prices are on the [pricing page](https://www.auto.dev/pricing).

## The three workflows

The workflow files are in the node's GitHub repository, in the [templates folder](https://github.com/auto-dot-dev/n8n-nodes-autodev/tree/main/templates). Download one, then use Import from File in a new n8n workflow.

| Workflow | Plan | Requests per run |
| --- | --- | --- |
| Market alert in Slack for one specific car | Free | 1 per check, 1 more when a listing is new |
| Deal sheet from a VIN | Growth | 4 |
| License plate check-in with open recalls | Scale | 2 |

## Where this is the wrong tool

It will not export a whole market. Every page of results is a request, and we left n8n's usual Return All switch out of the node so a single run cannot spend a month of calls. For a large pull, call the API directly and page through it.

The trigger polls, so you hear about a new listing at your next check and not the moment a dealer posts it.

Coverage is dealer inventory in the United States. A private seller's car will not appear, and neither will anything listed in another country.

## Questions

### Can an n8n AI Agent search car listings or decode a VIN?

Yes. Connect the Auto.dev node to the AI Agent node's Tool connector and pick an operation. We ran VIN decoding this way on 16 November 2026: the model filled in the VIN from the chat message and answered from the result. On a self-hosted n8n, set N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true, which is what we ran with.

### How do I decode a VIN in n8n?

Choose the VIN resource and the Decode operation, then enter a 17-character VIN. It returns the year, make, model, trim, body, engine, drive type, transmission and fuel, and it is on every plan.

### Can I use the HTTP Request node instead?

Yes. Send a GET request to https://api.auto.dev/listings with an Authorization: Bearer header holding your key, and add filters as query parameters. The node saves you building the filters, the new-listing trigger and the error messages yourself.
