An AI agent for Shopmonkey connects through an API key an admin creates under Settings, Integration, API Keys, and through webhooks that report changes to orders, messages, inspections and other records. Estimates, repair orders and invoices are all orders told apart by status, and webhooks report record changes, not business events. A service advisor should approve every customer message.
An AI agent for Shopmonkey is a small program that watches your shop's records (an estimate nobody answered, a repair order that finished while the car sat in the lot, a customer who declined a brake job in the spring) and drafts the next step for a service advisor to approve. Shopmonkey gives it two ways in: an API key an admin creates, and webhooks that tell the agent when something changed. What the agent should not do is send anything to a customer without a person reading it first.
This guide covers how the connection works, what the data looks like, where builds go wrong, and what stays with your advisors.
What Shopmonkey gives an agent to work with
Shopmonkey describes its API and webhooks page in plain terms: an API is "a door through which information and capabilities can be shared between two softwares," and a webhook is a kind of API driven by events instead of requests. The page says Shopmonkey can send information to other systems so they update on their own. It does not say which plans include access or how to get a key, so ask Shopmonkey or your account rep before you plan around it.
The developer site, shopmonkey.dev, links to the API overview, a webhooks page and an enterprise data streaming option. Third parties fill in the rest, and the quality varies. One of them, Carly, is a company that competes in this space, so read its claims as a starting point and confirm them in your own account.
How an agent connects
An API key from an admin. Carly's guide says an admin creates the key under Settings, Integration, API Keys, and that a key carries the same permissions as the person who made it. Two practical consequences follow. If that admin leaves or has their role narrowed, the integration starts failing with a 403. And the key can't be viewed again after you create it, so a lost key means a new one and a broken connection until it is swapped. Create keys from a dedicated account with only the access the agent needs.
A Supergood review adds that there is no sandbox or developer tier, so a builder tests inside a real shop's account, and that there is no fine-grained scope for keys. That review comes from a company that sells API tooling, so treat it as one view. The practical point holds either way: test with read-only work first.
Webhooks. Carly lists eleven kinds of records that send events when they are created, changed or deleted: appointments, customers, inspections, inventory, messages, orders, payments, purchase orders, users, vehicles and vendors. These are changes to records, not business events. One edit in the shop can fire several webhooks. An agent has to work out for itself that "this estimate has gone quiet" is a fact, because no event says so.
Two details matter for reliability. Delivery times out after about 55 seconds, so the receiving end should acknowledge fast and do its work afterward. And after repeated failures a webhook is switched off and missed events are not replayed on their own, according to the same guide. Someone has to notice and replay them.
One thing that surprises people: estimates are orders
In Shopmonkey's data, per Carly's guide, an estimate, a repair order and an invoice are all the same kind of record, an order, told apart by a status field. There is no separate estimate endpoint. An agent that follows up on quiet estimates therefore watches orders in the Estimate status and ignores the rest. A build that skips this will either miss estimates or text customers about finished jobs.
What an agent does around Shopmonkey
These are examples of the pattern, not a client story.
| Agent | Starts when | Reads | Drafts | Person approves |
|---|---|---|---|---|
| Estimate follow-up | An order in Estimate status has had no reply after a set number of days | Order lines, vehicle, customer messages | A personal text, ranked by dollar value | Service advisor |
| Declined work revisit | A customer is due back with declined inspection items | Inspection results, last visit, vehicle | A message naming the specific item | Service advisor |
| Ready for pickup | An order moves to complete and the car is still on site | Order status, customer contact | A pickup message | Front desk |
| Owner morning report | Every morning | Orders, payments, appointments | One summary | None, it only reads |
Setup steps and what you need
- A Shopmonkey admin willing to create a limited key and add a webhook.
- Two or three jobs, in order. Quiet estimates and declined work usually come first.
- Access to the other systems in play: your phone provider, QuickBooks, review accounts. Supergood reports that Shopmonkey's built-in catalog is short (QuickBooks Online, CARFAX, PartsTech, Nexpart and RepairLink), so most other connections need custom work.
- One advisor per agent approving drafts for the first few weeks.
Start with a person approving every message and loosen it only after you have read enough drafts to trust them. We explain the model in human-in-the-loop AI.
Limits and risks
- Safety work stays human. An agent never tells a customer a car is safe to drive or talks anyone out of a brake or steering repair.
- Prices and warranty. Discounts, goodwill repairs and warranty calls belong to the advisor.
- Wrong customer. Match on phone number and vehicle, not just a name.
- Double messages. If Shopmonkey's own messaging and an agent both text about the same car, pick one for each stage.
- Upkeep. Keys, permissions and events change. Someone has to own that, which is the reason for managed AI operations.
Where Cortex fits
Cortex builds AI agents that work inside the software you already run, with a person approving anything that goes to a customer. We are not a Shopmonkey partner or a certified app, and we will say so when Shopmonkey's own tools are enough. See what we connect on integrations and how this looks for auto repair. For recovering work that fell off the board, read about declined work. If your shop runs a different system, see AI agents for Tekmetric or AutoLeap.
The free AI Operations Audit looks at your shop software, phones and books in 30 minutes and tells you which job to hand an agent first.
Questions people ask
Does Shopmonkey have an API?
Yes. Shopmonkey's API and webhooks page describes both, and its developer site is shopmonkey.dev. The page does not say which plans include access, so confirm that with Shopmonkey before you plan a build.
Does Shopmonkey support webhooks?
Yes. A third-party guide lists eleven record types that send events, including orders, messages, inspections and payments. These are record changes, so an agent has to work out for itself that an estimate has gone quiet.
Can I connect ChatGPT to Shopmonkey?
We found no native ChatGPT connector. An assistant would need an admin-created API key or a webhook feed, plus a place where a service advisor approves drafts before anything reaches a customer.
Is there a sandbox to test an AI integration?
One third-party review reports there is no sandbox or developer tier, so testing happens in a real shop account. Start with read-only work and give the agent a key with limited access.
What happens if the admin who made the API key leaves?
A third-party guide says a key carries the same permissions as its creator, and the integration fails with a 403 if that person is offboarded or their role is narrowed. Create keys from a dedicated account.
Sources
- API & Webhooks Integration, Shopmonkey
- Shopmonkey API documentation, Shopmonkey
- Shopmonkey API guide, Carly
- Shopmonkey API report card, Supergood
Originally published at buildcortex.dev.
Top comments (0)