Carix
E-commerceConnect AI agents to Carix, a dealer vehicle management system from German vendor HT Automotive. Agents read the dealer's vehicle inventory and resolve the dealer-specific field set at runtime, feeding listings and stock reports downstream. The API is pull-only, with no write operations.
What This Integration Enables
Carix, from the German vendor HT Automotive, is the vehicle management system behind a lot of car dealer websites, and this connector is deliberately small because the API is. Carix is pull only: it exposes no create, update, delete, or subscription operations, so an agent reads a dealer's inventory and reads the metadata describing it, and that is the entire surface. Five actions. That is a thesis rather than a gap. The system of record for a vehicle is the dealer's own back office, where a salesperson changes a price after a conversation on the forecourt, and a connector that offered to write into it would be offering something the vendor does not, and something the dealer would be right to refuse. What this integration is genuinely for is taking a live inventory that already exists and putting it somewhere useful: a listing page, a search widget, a spreadsheet, a warehouse, or an alert to a customer who has been waiting for a particular car.
The mechanics are unusual enough to matter. Authentication is two query string credentials sent on every request, m for the dealer Mandant-KDNr configured as Customer Number and t for the API Token, rather than a header or an OAuth flow. Failures are the part to plan around: Carix returns a body of the form Error (<code>): <message>, for example Error (101): Missing Mandant or Error (201): Invalid Mandant, with an HTTP 200 status and an HTML content type. This connector detects a response beginning with Error (, parses the code and message, and raises a real error, so a flow fails at the step that failed instead of carrying an error string forward as if it were a vehicle. The response payload shape is not documented in prose and is dealer specific, which is why List Fields and Get Field Detail are not conveniences but part of the working pattern: they are how an agent learns which fields exist on this account, which of them are searchable, and what values a field can hold. Fields whose names begin with dyna_ are dealer maintained and can change or disappear between accounts and over time, so nothing downstream should hard code them. Filters apply only to fields flagged as searchable in List Fields; anything else is ignored server side, silently. And the image resolution parameter splits along a line worth knowing: mini at 105px, small at 160px, mida at 186px, midb at 290px, midc at 600px, and midd at 141px come without a watermark, while midi at 320px, xl at 550px, xxl at 800px, xxxl at 1200px, and xxxxl at 1600px carry the Carix watermark. Omit it and Carix defaults to small. There are no triggers, because there is nothing to subscribe to, so a flow polls on a schedule. Agents read the feed. The moment that feed becomes a published price or an email to a customer is where human-in-the-loop orchestration belongs.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A listing surface that stays in step with the forecourt
On a schedule the agent calls List Fields first, before touching the inventory, because that call reports which fields this dealer's account actually carries and which of them are searchable. It confirms that every field the downstream template depends on is present, then calls List Vehicles with the filters, multi field sorting, paging, and image resolution the listing needs, choosing a resolution from the unwatermarked set for a dealer's own site. Each vehicle is compared against the previous run to separate genuine arrivals from price changes and from cars that have sold. New rows append to a working sheet in Google Sheets or into a warehouse table, and the change summary posts to Slack for whoever owns the listings. Because Carix answers a failure with an HTTP 200 and a text body, the run's error handling is not decorative: without it, a run against a mistyped Customer Number publishes an error message where a car should be.
A faceted search widget built from the dealer's own vocabulary
A dealer wants a search mask on their site with real counts behind each option. The agent calls Get Vehicle Navigation, which takes the same searchable field filters as List Vehicles and returns the counts and available values for facets such as fuel type and body type within the active filter, so the options shown reflect the inventory as it stands rather than a hardcoded list from a year ago. Get Field Detail fills in the complete list of possible values for a given field, which is what a select control needs, and List Fields decides which controls are even offered, since a filter on a field that is not flagged searchable is accepted and then ignored. The result is a search experience that matches this dealer's stock, and that keeps matching it when the dealer adds a dyna_ field for something specific to their business.
A waiting customer matched to a car that has just arrived
A buyer has told a salesperson what they are looking for, and that specification sits in a CRM or a sheet. On a schedule the agent runs List Vehicles filtered on the searchable fields that correspond to the request, and where a new match appears, calls Get Vehicle for the full detail and images at the resolution the message will use. It assembles the alert: the vehicle, the price the feed reports, the photos, and the note about which fields came from dyna_ values that the dealer maintains by hand. Then it stops, because the next step is an email to a real customer through Brevo or Gmail quoting a price, and an email cannot be recalled. The salesperson who knows the car sees the draft first.
Human-in-Loop Highlight
This connector cannot write anything to Carix, so the irreversible act is not inside it. It is one system downstream, at the moment a read becomes a published price or a message to a buyer, and Carix gives an agent a specific reason to hesitate there. The response payload shape is dealer defined rather than documented, and fields beginning with dyna_ are maintained by the dealer and can be renamed or removed at any point. A listing template built last quarter against dyna_finanzierung or a dealer's own equipment field keeps working right up until somebody in the back office renames it, at which point List Vehicles returns rows that are perfectly valid and simply missing the value the page depends on. Nothing errors. The page renders with an empty price field, or the alert goes out describing a car without the option the customer specifically asked about. The brand_url manufacturer logo has a quieter version of the same problem, since it is only populated for authorized or contract dealers, and the image resolution parameter has a third, because the midi, xl, xxl, xxxl, and xxxxl sizes carry the Carix watermark while mini, small, mida, midb, midc, and midd do not, and a template that switched to a larger image for a hero shot can put a watermark across a dealer's own homepage. So the agent checks the shape before it trusts the contents. Each run it calls List Fields, compares the returned field set against the fields the downstream template consumes, and where something is missing it posts to the listings owner in Slack: "Inventory sync for Autohaus Perner. 14 new vehicles, 6 price changes, 3 sold. Two fields the listing template uses are no longer returned by List Fields: dyna_garantie and dyna_finanzierungab. 11 of the 14 new vehicles would publish with those sections empty. The image resolution is set to xl, which is one of the watermarked sizes. Publish all 14 as they are, publish only the 3 that are complete, or hold until the field names are re-mapped?" A person answers, and the agent publishes what was released. This is the digital andon cord applied to a read-only feed: the connector has no destructive operation of its own, so the gate goes on the first place its output stops being reversible, which is a public page and a customer's inbox.
Agent Capabilities
5 actionsInventory
3- List Vehicles Returns all vehicles in the dealer inventory matching the current search scope, with optional filtering on searchable fields, paging through hits per page and hit position, multi field sorting, sort direction, and image resolution selection. Filters take an object of field name and value pairs, and only fields flagged as searchable in List Fields are honored; the rest are ignored server side. The payload shape is defined by the dealer account and can include dynamic fields whose names begin with `dyna_`.
- Get Vehicle Navigation Returns navigation data for building a search mask over the current inventory, such as counts and available values for facets like fuel type and body type within the active filter. It takes the same searchable field filters as List Vehicles, so the facets reflect the search scope a visitor is actually in rather than the whole stock.
- Get Vehicle Returns the full detail of a single vehicle by its Carix vehicle ID, optionally selecting the image resolution used for image URLs in the response. The payload shape is defined by the dealer account and can include `dyna_` fields.
Field metadata
2- List Fields Returns the available data fields for a Carix table with their types and attributes, including whether each field is searchable. Because the payload shape is not documented in prose and is discoverable only at runtime, this is the call that tells a flow which filters will work and which fields a downstream template can rely on. Run it before the inventory read, not after a page breaks.
- Get Field Detail Returns the definition of a single field including its complete list of possible values. This is what populates a value picker or validates a filter input before List Vehicles is called with it.
Frequently Asked Questions
What can FlowRunner do with Carix?
FlowRunner agents can run List Vehicles, Get Vehicle Navigation, and Get Vehicle in Carix, plus 2 more actions.
Does connecting Carix to FlowRunner require OAuth?
Carix uses a custom authentication method to connect to FlowRunner.
Can Carix trigger a FlowRunner workflow automatically?
Carix doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Carix
$100 in credits. No card required. Connect in minutes.