Skip to content

Open Recall Checker · Automotive

Tell customers about open recalls before they ask

Each new repair order is checked against NHTSA's free recall data. Your advisor gets a plain-words rundown in Slack and approves the customer heads-up email.

Available now $129 one-time · never renewsIncluded in Enterprise
Get this agent See how it works

Free account to start. Buying and running live need a paid plan.

  • Starts from an event in a connected app
  • 2 AI steps
  • A person approves before it acts
  • About 25 min to set up

Sound familiar?

The job, before and after this agent.

What it feels like today

  • “A customer hears about a safety recall from a letter months later and asks why we didn't say.”
  • “Looking up recalls for every RO by hand doesn't happen on a busy day.”
  • “Recall notices are written in language customers don't understand.”

What you get with the agent

  • VIN decoded to make, model and year with NHTSA's free vPIC API; recall campaigns listed with NHTSA's free Recalls API.
  • Each campaign explained in plain words (component, risk, remedy), with do-not-drive and park-outside advisories flagged.
  • Your service advisor alerted in Slack with every campaign.
  • The customer heads-up email goes only after the advisor approves; the row is then marked with the date and campaign numbers.
  • Missing or impossible VINs sent to the advisor to check by hand.

Before

A sedan comes in for an oil change with an open campaign nobody checks. The customer hears about it from another shop.

After

The RO row goes in, your advisor sees two campaigns explained in Slack, confirms the VIN and approves a heads-up email that points the customer to the nhtsa.gov lookup.

How it works

The whole workflow, step by step.

Starts from each new row in your repair-order or customer-vehicles sheet (name, email, VIN). The VIN is decoded to make, model and year with NHTSA's free vPIC API, and NHTSA's free Recalls API lists the campaigns for that vehicle. AI explains each one in plain words — component, risk, remedy — and flags “do not drive” and “park outside” advisories. Your service advisor is alerted in Slack, and the customer heads-up email waits for the advisor's approval before it is sent; then the row is marked checked with the campaign numbers. Missing or undecodable VINs go to the advisor to check by hand. NHTSA's public API lists recalls by make, model and year — not by VIN, and not whether the repair is already done — so the email says the recall “may apply” and points to the VIN lookup on nhtsa.gov. US vehicles only. It doesn't perform recall work or claim dealer reimbursement.

  1. TriggerNew vehicle in your sheet
  2. AI stepCheck the VIN and contact
  3. LogicVIN usable?
    • VIN missing or invalid:Ask the advisor to check by hand
    • VIN ok:Decode the VIN (NHTSA vPIC)
  4. App callDecode the VIN (NHTSA vPIC)
  5. LogicDecoded?
    • Not decoded:Ask the advisor to check by hand
    • Decoded:List recalls (NHTSA Recalls API)
  6. App callAsk the advisor to check by hand
  7. OutputSent to an advisor
  8. App callList recalls (NHTSA Recalls API)
  9. AI stepExplain the recalls
  10. LogicRecalls listed?
    • None listed:Mark the row checked
    • Recalls, no email:Alert the service advisor
    • Recalls listed:Alert the service advisor
    • Recalls listed:Approve the customer heads-up
  11. App callAlert the service advisor
  12. OutputAdvisor alerted
  13. Human approvalApprove the customer heads-up
    • Approved:Email the customer
    • Doesn't apply:Not emailed
  14. OutputNot emailed
  15. OutputEmail the customer
  16. App callMark the row checked
  17. OutputRow marked

This is the workflow that opens in your workspace when you set the agent up. Every step can be edited.

  1. Step 1New vehicle in your sheetStarts a run for each row added to your repair-order or customer-vehicles sheet (name, email, VIN), checked on your plan's schedule interval.
  2. Step 2Check the VIN and contactAI reads the row, cleans up the VIN (17 characters, no I, O or Q) and picks out the customer's name and email. A missing or impossible VIN goes to your advisor to check by hand.
  3. Step 3VIN usable?A missing or impossible VIN can't be looked up: your advisor is asked to check it by hand. The rest are decoded by NHTSA.
  4. Step 4Decode the VIN (NHTSA vPIC)Calls NHTSA's free vPIC API (vpic.nhtsa.dot.gov) to decode the VIN into make, model and model year. No key is needed.
  5. Step 5Decoded?When NHTSA can't decode the VIN into a make, your advisor is asked to check it by hand; otherwise the recall list is fetched.
  6. Step 6Ask the advisor to check by handPosts the row to your service advisors' Slack channel: the VIN is missing, invalid or couldn't be decoded, so the recall check needs a person.
  7. Step 7Sent to an advisorThe run history keeps the row and why it couldn't be checked automatically.
  8. Step 8List recalls (NHTSA Recalls API)Calls NHTSA's free Recalls API (api.nhtsa.gov) for the recall campaigns listed for that make, model and model year. No key is needed.
  9. Step 9Explain the recallsAI explains each campaign in plain words (component, risk, remedy), flags “do not drive” and “park outside” campaigns, and drafts the advisor's Slack alert and the customer's heads-up email — always as recalls that “may apply”.
  10. Step 10Recalls listed?No recalls: the row is marked checked. Recalls listed: your advisor is alerted in Slack and, when there's an email address, the heads-up email waits for approval.
  11. Step 11Alert the service advisorPosts the vehicle, the customer and every campaign (with “do not drive” and “park outside” flags) to your advisors' Slack channel.
  12. Step 12Advisor alertedThe run history keeps the alert that was posted.
  13. Step 13Approve the customer heads-upThe service advisor confirms the VIN on nhtsa.gov, edits the heads-up email if needed and approves; nothing is sent before that.
  14. Step 14Not emailedThe advisor rejected the heads-up (the recall doesn't apply or was already done). The Slack alert stays.
  15. Step 15Email the customerSends the approved heads-up from your workspace's sender, with replies going to your service desk.
  16. Step 16Mark the row checkedWrites the result (“Recall check: none listed” or “Recall heads-up emailed”), the date and the campaign numbers into the row, starting at your status column.
  17. Step 17Row markedThe row shows the recall check result and date.

Example run

What goes in, and what comes out.

Example with fictional data

Comes in

Fictional RO-10457: 2018 Honda Accord, VIN on file, customer Dana with an email address.

The agent produces

VIN decoded, campaigns for that make, model and year listed and explained in plain words, advisor alerted in Slack, and a may-apply heads-up email waiting for approval.

What you need

Everything it takes to run it.

About 25 minutes from purchase to live. A checklist above the canvas takes you through each step.

Plan

Included in Enterprise; on other paid plans it's $129 once. Agents run live on paid plans, from Basic ($39/mo).

Your AI key

Connect any of 14 AI providers on your own key. Your provider bills usage directly, at cost; we add no markup.

Apps

Checklist

  • A paid plan (agents run live on paid plans).
  • An AI provider key (Settings → AI Providers).
  • Google Sheets and Slack, connected in Settings → Integrations.
  • Two HTTP / Custom API connections with no key: https://vpic.nhtsa.dot.gov/api and https://api.nhtsa.gov (free public NHTSA APIs).
  • A sheet with the customer's name, email and VIN per vehicle, and empty status columns.

Setup, about 25 minutes

  1. Connect your AI provider. The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
  2. Connect Google Sheets. Connect the Google account that can open and edit your vehicles sheet (Settings → Integrations → Google Sheets).
  3. Connect NHTSA (two HTTP / Custom API connections). In Settings → Integrations → HTTP / Custom API add two connections, both with authentication “None” (the APIs are free and need no key): “NHTSA vPIC” with base URL https://vpic.nhtsa.dot.gov/api, and “NHTSA Recalls” with base URL https://api.nhtsa.gov. Two connections are needed because the hosts differ. Both are public US government APIs; see nhtsa.gov for their terms.
  4. Connect Slack. Connect the Slack workspace your service advisors use (Settings → Integrations → Slack).
  5. Pick your vehicles sheet. Open the trigger, pick your Google account, paste the spreadsheet link and the tab new vehicles are added to.
  6. Pick the NHTSA connections. Open “Decode the VIN (NHTSA vPIC)” and pick the vPIC connection, then “List recalls (NHTSA Recalls API)” and pick the Recalls connection.
  7. Describe your shop. Open “Explain the recalls” and replace the placeholder with your shop name, phone, booking link, how you help with recalls and your sign-off.
  8. Pick the advisors' channel. Open “Ask the advisor to check by hand” and “Alert the service advisor” and pick your account and channel in each. Invite the app to private channels first (/invite @Fluxo Flow).
  9. Add your service desk inbox. Open “Email the customer” and enter the address customers' replies should go to.
  10. Pick where rows are marked. Open “Mark the row checked”, pick the same account, spreadsheet and tab as the trigger, and enter the letter of your first empty status column.
  11. Test it with Dry Run. Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
  12. Switch the trigger on. Open the trigger and click “Activate app trigger”. New rows are picked up on your plan's schedule interval; rows already in the sheet aren't processed.

Is it a fit?

Who it's for, and what it won't do.

Built for

  • Independent repair shops
  • Service advisors and service managers
  • Used car dealers checking past customers

What it doesn't do

  • NHTSA's public API lists recalls for the make, model and year, not for this VIN, and doesn't show whether the repair is already done — so the email says the recall “may apply” and points to the VIN lookup on nhtsa.gov. Your advisor confirms the VIN before approving.
  • US vehicles only (NHTSA data). Models named differently in NHTSA's recall database may return no campaigns.
  • It doesn't perform recall work, book dealer appointments or claim dealer reimbursement; recall repairs are done free by an authorized dealer.
  • Nothing is emailed to a customer without the advisor's approval. Rows already in the sheet before activation aren't processed.

We list the limits up front so you can decide before you buy.

Price

$129 one-time

Per workspace. It never renews.

Available now
  • Included at no extra cost on Enterprise.
  • Buying and running it live need a paid plan, from Basic ($39/mo).
  • Dry Run costs nothing: simulated AI and app calls, nothing sent.
  • AI usage is billed by your own provider, at cost. No AI credits to buy from us.
Get this agent See how it works

One-time agent purchases aren't covered by the 30-day money-back guarantee. Refund policy

FAQ

Questions about Open Recall Checker.

Does it know this exact car is affected?

No. NHTSA's public API lists recalls by make, model and year, not by VIN, and doesn't show whether the repair is done. The email says the recall may apply and links the nhtsa.gov VIN lookup; your advisor confirms first.

Does it do recall work or claims?

No. It doesn't perform recall work, book dealer appointments or claim reimbursement. US vehicles only.

How long is setup?

About 25 minutes: connect Google Sheets and Slack, add two free NHTSA connections (no key), pick your sheet, describe your shop and run a Dry Run.

What does it cost?

NHTSA data is free. The agent is a one-time unlock that never renews; live runs need a paid plan and your own AI key.

Does it know whether this exact car is affected?

No. NHTSA's public recall API lists campaigns by make, model and model year, not by VIN, and doesn't show whether the repair was done. The email says the recalls “may apply” and links the customer to the VIN lookup on nhtsa.gov; your advisor confirms the VIN before approving.

What should the sheet have?

One row per vehicle with the customer's name, email and the 17-character VIN, plus two or three empty columns at the end for the agent (status, date, campaigns). Column names can vary. For a one-off sweep of past customers, paste them into the sheet.

Does it cost anything to use NHTSA?

No. vPIC and the Recalls API are free public US government APIs with no key. Each host is its own HTTP / Custom API connection with authentication “None”.

Is this a subscription?

No. Open Recall Checker is a one-time purchase of $129 per workspace and never renews. The Enterprise plan includes it at no extra cost. Running it live needs a paid plan (from Basic ($39/mo)), and your AI provider bills you directly for usage.

Can I test it before it touches real data?

Yes. Once it's set up in your workspace, Dry Run plays every step on sample data with simulated AI and app calls: nothing is sent and nothing in your apps changes. Switch the trigger on only when you're happy.

Put Open Recall Checker to work.

Free account, no credit card. Your Agents page opens with Open Recall Checker ready to buy and set up, then Dry Run it before it goes live.

Get this agent See how it works