{
  "object": "doc",
  "title": "How do I use Cartroute from n8n, Zapier or Make?",
  "description": "Configure a generic HTTP request step against the API.",
  "section": "Agents and integrations",
  "url": "https://cart-route.com/docs/guides/no-code",
  "updated": "2026-09-23",
  "prev": "https://cart-route.com/docs/guides/typescript",
  "next": "https://cart-route.com/docs/guides/recommendations",
  "text": "In n8n, Zapier or Make, add a generic HTTP request step: method `GET`, URL `https://cart-route.com/api/v1/search`, a query parameter `q`, and a header `Authorization` with the value `Bearer cr_live_...`. The JSON response can be mapped into later steps directly; the fields most workflows need are listed below.\n\r\n\r\n\n## Which settings does the HTTP step need?\n\r\n\r\n  \r\n\n| Setting | Value | \r\n    \r\n\n| Method | `GET` | \r\n\n| URL | `https://cart-route.com/api/v1/search` | \r\n\n| Query parameters | `q` = the product, optionally `max_price`, `condition` = `new`, `limit` = `3` | \r\n\n| Header | `Authorization` = `Bearer cr_live_...` (store it as a credential, not in the step text) | \r\n\n| Response format | JSON | \r\n    \r\n\n\r\n\n\r\n\r\n\n## Which response fields should I map?\n\r\n\r\n  \r\n\n| Path | Meaning | \r\n    \r\n\n| `results[0].title` | Best-matching product. | \r\n\n| `results[0].price_summary.best_retailer` | Where it is cheapest. | \r\n\n| `results[0].price_summary.best_effective_price_usd` | What it costs there, shipping and coupon included. | \r\n\n| `results[0].price_insight.verdict` | `good_time_to_buy`, `typical_price` or `above_recent_average`. | \r\n\n| `results[0].offers[0].buy_url` | Link to buy. | \r\n\n| `credits.remaining` | Balance, for a low-credit alert. | \r\n    \r\n\n\r\n\n\r\n\r\n\n## What is a useful first workflow?\n\r\nA daily price-drop alert: a schedule trigger, the HTTP step with a fixed query, a filter that continues only when `price_insight.verdict` equals `good_time_to_buy`, and an email or Slack step with the retailer, price and `buy_url`. It costs one credit a day.\n\r\n\r\n\n## How do I handle errors in a workflow?\n\r\nTurn on the step's \"continue on error\" option and branch on the HTTP status: `402` means out of credits, `429` means retry later. The body's `detail` is readable enough to send as-is in a notification."
}