No-Code Tire API Automation with n8n
Import ready-to-use n8n workflows for tire fitment automation without writing any code
The Problem: Tire Data Integration Without Code
Integrating tire fitment data into your applications has always required API knowledge or hiring developers. Not anymore. We've published four ready-to-import n8n workflows for tire.vdim.app's Tire Size API that automate vehicle lookups, tire dimension retrieval, reverse fitment matching, and rate-limit monitoring—all without writing a single line of code.
What You Get: 4 Production-Ready n8n Workflows
Each workflow is a reusable automation template you can import into n8n and run immediately. All four follow the same simple pattern:
[ Trigger ] → [ Set Inputs ] → [ HTTP Request ] → [ Use the Data ]No custom code required. Every workflow uses standard n8n nodes and your single API key credential.
Workflow #1: Cascading Vehicle Lookup
Use Case: Power dependent dropdowns in a tire fitment form. Let users drill down Year → Make → Model → Trim → Tire Size.
API Endpoints Used:
GET /by_vehicle/makeGET /by_vehicle/modelGET /by_vehicle/trimGET /by_vehicle/tiresize
Why It Works: Each step filters vehicle options. The final response includes OE tire sizes for that exact make, model, and trim combination—perfect for catalog enrichment or spec sheets.
💡 Pro Tip: Vehicle trim values are exact strings (e.g., "LE AWD", not "LE"). The workflow shows how to discover valid values at each step.
Workflow #2: Tire Dimensions Lookup
Use Case: Get tire width, aspect ratio, and diameter for any vehicle in one call. Perfect for spec sheets and vehicle validation.
Single API Endpoint:
GET /tire_dimensions?year=2020&make=Toyota&model=CamryResponse Example:
{
"dimensions": [
{
"width": "225",
"aspectratio": "65",
"diameter": "17",
"tiresize": "225/65R17 102H"
}
]
}Workflow #3: Reverse Tire Lookup
Use Case: Start with a tire size and find every vehicle that uses it. Perfect for "fits these vehicles" marketing pages and inventory cross-referencing.
Two Ways to Query:
Option 1 - Full tire size:
GET /reverse_lookup?tiresize=225/60R16Option 2 - Individual dimensions:
GET /reverse_lookup?width=225&aspectratio=60&diameter=16Response: Array of vehicles (year, make, model, trim) that use that tire size. Instantly see compatibility across your entire vehicle database.
Workflow #4: Usage & Rate-Limit Guard (NEW)
Use Case: Monitor your API quota and prevent runaway bulk jobs. Automatically branch when quota is running low.
Endpoint:
GET /usageWorkflow Logic:
✓ Check Usage → Extract fields → IF (Daily Remaining < 50?) → Quota OK or Low Quota branch
Perfect for: Bulk import jobs that can wait. Place this guard at the start—only proceed on the "Quota OK" branch, send a Slack/email alert on "Low quota".
New Subscription Plans: More Requests, Same Simplicity
We've simplified the subscription tiers to be clearer about what each plan supports:
| Plan | Daily Requests | Hourly Limit | Best For |
| Free | 300 | 100/hr | Testing & small projects |
| Starter | 5,000 | None | Growing applications |
| Pro | 50,000 | None | Large-scale apps |
| Business | 80,000 | None | High-volume, mission-critical |
Every response includes live headers (X-RateLimit-Limit, X-RateLimit-Remaining, X-Subscription-Type), so you always know where you stand. Workflow #4 queries the full picture on demand.
API Reliability Improvements
Previously: Querying a vehicle that didn't exist could return a generic "Database error occurred" (HTTP 500). That made automation fragile and hard to debug.
Now: Those requests return a clean 404 with helpful suggestions (check the year, verify the make/model, etc.), so your n8n workflows can branch on "not found" without treating it as an outage.
Getting Started: 5 Minutes to Your First Workflow
Step 1: Get an API Key
Sign up for free at account-tire.vdim.app. You get 300 API calls/day immediately.
Step 2: Create an n8n Credential (Once)
In n8n, go to Credentials → Create New. Type "Header Auth", name it "Tire API", and add:
Header name: x-api-key
Header value: YOUR_API_KEY_HEREAll four workflows reuse this single credential.
Step 3: Import a Workflow
Download a workflow `.json` from our GitHub repo. In n8n: Workflows → Import from File → select the JSON.
Step 4: Assign Credentials & Execute
Click each HTTP Request node, assign the "Tire API" credential from the dropdown, and click Execute. Done.
Real-World Use Cases
Use Case 1: Daily Inventory Sync
Use Workflow #2 (Tire Dimensions) scheduled nightly to fetch OE tire specs for 1,000 vehicles in your catalog. Store results in a database. Starts under 100 API calls/day even with hourly runs.
Use Case 2: Website Form Dropdowns
Use Workflow #1 (Cascading Lookup). Hook the n8n webhook output to your website's form. Year/make/model inputs trigger the workflow and return valid trim options in real-time.
Use Case 3: Marketing Page Generator
Use Workflow #3 (Reverse Lookup) to generate "Fits these vehicles" landing pages for each tire size in your catalog. Rebuild the pages weekly via Workflow #4 rate-limit guard.
Ready to Automate Your Tire Workflows?
No code. No API expertise. Just import and run.
Workflows on GitHub
API Docs & n8n Guide
Get a Free API Key
Questions or need help? Visit tire.vdim.app/contact or check the n8n section in our API docs for in-depth workflow walkthroughs.