Autovit
E-commerceConnect AI agents to Autovit, the Romanian car classifieds marketplace. Agents publish and update dealer listings, apply promotions to boost visibility, and read the make, model, and body-type taxonomy behind each advert.
What This Integration Enables
Autovit is a classifieds marketplace, and that changes what a write means. An advert is not a row in your inventory system, it is a public shop window in Romania with a marketplace URL that buyers call the number on. This connector reaches Autovit through the OLX Group Partner API, which is the same interface serving several OLX Group marketplaces, and the Site URN configuration item selects which one. Adverts are fully writable: Create Advert publishes, Update Advert amends, Activate Advert and Deactivate Advert control visibility without destroying the record, and Delete Advert schedules removal. Get Advert Metadata and List Adverts Metadata read back the state that actually matters after a write, meaning the moderation status, the marketplace URL and the last error. Get Category Taxonomy is the operation a flow cannot skip, because Create Advert requires a category URN and the attributes that category defines, and those attribute URNs and their allowed values are discoverable only from the taxonomy.
Three properties of this platform decide whether an automated listing pipeline behaves. Moderation is the first: advert changes are submitted for platform review, and the last_action_status a call returns reflects the transition you requested rather than the state Autovit ended up in. A flow that treats a successful response as a published listing will report stock as live that is still in review, so the honest pattern is to write, then read List Adverts Metadata on a later pass and reconcile. The second is authentication, which has two layers that are both required on every advert, taxonomy and promotion call: an OAuth2 access token obtained by connecting an account and refreshed automatically as it expires each hour, and a separate partner X-API-KEY header identifying your integration, which is not the OAuth client ID and is issued by Autovit on request. The third is that this connector has no triggers at all. The Partner API publishes no webhook subscription surface, so nothing on Autovit can start a flow. Everything here runs on a schedule or on an event from your own systems, and moderation outcomes are discovered by polling List Adverts Metadata and comparing status against the previous run. Agents keep the forecourt and the marketplace saying the same thing. The spend that buys visibility is where human-in-the-loop oversight belongs.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Stock that lists itself, with the taxonomy resolved first
A dealer group adds fourteen cars to its management system overnight. On the morning run the agent reads the new records, and before it builds a single payload it calls Get Category Taxonomy for the target category to collect the category URN, the child categories and the attribute URNs with their allowed values. This ordering matters: a make, a fuel type or a body style expressed the way the dealer system spells it is not the same as the attribute value Autovit accepts, and a payload assembled from guesses fails at moderation rather than at the call. With valid URNs in hand the agent calls Create Advert for each vehicle with its contact details, location, images and price, logs the returned advert UUID back against the stock record in Google Sheets so the two systems are joined by an identifier rather than by a title, and stops. On the next pass it calls List Adverts Metadata and compares moderation status against what it recorded, posting only the changes to the sales channel in Slack. A rejected advert with a last error attached goes to a person; an approved one with its marketplace URL goes back to the stock record.
A sale that takes the advert down with it
The most expensive failure on a classifieds site is not a missing listing, it is a live one for a car that sold on Tuesday. The agent watches the dealer system for status changes and reacts on the same cycle as the stock sync. A vehicle marked sold gets Deactivate Advert, which removes it from the marketplace while keeping the record and its history intact, so a deal that falls through can be answered with Activate Advert rather than a fresh listing and a new URL. A vehicle genuinely gone from the estate, an auction return or a trade sale, gets Delete Advert, which schedules removal and sets the last action status to TO_DELETE. Because the two are not equivalent, the flow does not decide between them from a single field: a sold flag drives deactivation automatically, and deletion is only ever proposed, never taken.
Promotion spend aimed at the stock that needs it
Ageing stock is the reason promotion packages exist. Once a week the agent reads days on the forecourt from the dealer system, calls List Adverts Metadata to confirm which of those vehicles are actually live and approved rather than in moderation, and calls Get Active Promotions For Advert on each candidate to see what is already running and when it expires. That last read is what stops a package being stacked on an advert that is already featured for another eleven days. Get Available Promotions returns the packages the marketplace offers with their codes, descriptions and allowed durations in days, and the agent builds a proposal: which adverts, which package, how many days, and what is already active on each. A person picks from that list, and only the released rows reach Apply Promotion.
Human-in-Loop Highlight
Apply Promotion is the operation to gate, and the argument for it is an absence rather than a risk. This connector can apply a promotion package to an advert for a chosen number of days, and it can tell you afterwards what is running through Get Active Promotions For Advert. What it cannot do, because the surface does not offer it, is take one back. There is no cancel, no refund, no shorten. Once Apply Promotion succeeds against an advert UUID, the package is committed for its full duration and the only remaining lever is the report that shows you it happened. That asymmetry is what makes it a decision rather than a step. The errors it invites are ordinary ones. An advert UUID from a stale export points the package at a vehicle that sold last week, and the money buys visibility for a car nobody can be sold. A duration is read from the wrong column and a seven day package becomes a thirty day one, which Get Available Promotions will happily accept because thirty is an allowed duration. A loop over a stock list with no guard applies a package to every advert in it rather than to the six that needed help. So the agent assembles the case and hands over the decision. It reads Get Available Promotions for the codes and their allowed durations, List Adverts Metadata to confirm each target is live and past moderation rather than pending, and Get Active Promotions For Advert to show what is already committed on each one, then posts to the sales manager in Slack: "Promotion proposal, 6 adverts over 45 days on the forecourt. Package BOOST_7D, 7 days each. 2 of the 6 already carry an active package: Skoda Octavia 2019 expires in 11 days, Ford Kuga 2020 expires in 3 days. 1 advert is still in moderation and would be promoted while invisible: BMW 320d 2021. Apply Promotion cannot be reversed once it succeeds. Promote all 6, promote the 3 that are live and unpromoted, or hold?" A person answers once, and the agent applies only what was released. Delete Advert sits behind the same gate for a related reason: it schedules a public listing for removal, and the marketplace URL that goes with it is the address buyers have already bookmarked. This is the digital andon cord placed on the two operations here that cost money or cost a listing.
Agent Capabilities
11 actionsAdverts
7- Create Advert Creates a listing on Autovit through the OLX Group Partner API. The advert is submitted for moderation and enters the platform workflow. Supply the category URN and its required attributes, which you retrieve with Get Category Taxonomy, along with contact details, location, images and price. The target marketplace comes from the Site URN configuration item.
- Update Advert Updates an existing advert by its UUID. Send the full advert payload with the changed fields, and expect the update to be re submitted for moderation. Some status transitions are rejected by the platform rather than applied.
- Delete Advert Deletes an advert by its UUID. The advert is scheduled for removal and its last action status becomes TO_DELETE, so the public listing and its marketplace URL go with it.
- Activate Advert Activates an advert by its UUID so it becomes visible on the marketplace. Activation is subject to platform moderation and to the status rules Autovit enforces.
- Deactivate Advert Deactivates an advert by its UUID so it is no longer visible on the marketplace, without deleting it. This is the reversible counterpart to Delete Advert and the right response to a vehicle leaving stock.
- Get Advert Metadata Retrieves the current metadata and state of one advert by its UUID, including moderation status, marketplace URL, timestamps and any last error. This is how a flow finds out what actually happened to a write.
- List Adverts Metadata Retrieves metadata and state for every advert on the authenticated partner account, returning each advert's UUID, status, marketplace URL and timestamps. With no trigger available, this is the polling read that detects moderation outcomes between runs.
Taxonomy
1- Get Category Taxonomy Retrieves the taxonomy for a category on the configured marketplace, including the category label, its child categories and the attributes required or accepted when creating an advert there. Use it to discover valid category URNs, attribute URNs and their allowed values before building any advert payload.
Promotions
3- Get Available Promotions Retrieves the promotion packages available on the configured marketplace, each with its code, description and allowed durations in days. The promotion code field elsewhere is backed by a picker populated from this operation.
- Apply Promotion Applies a promotion package to an advert by its UUID for a chosen duration in days. Codes and durations come from Get Available Promotions. There is no counterpart operation that removes or shortens an applied package, which is why this one belongs behind a person.
- Get Active Promotions For Advert Retrieves the promotions currently active on an advert by its UUID, including each promotion code, its status, its expiry timestamp and any marketplace references. Read this before proposing new spend on an advert.
Frequently Asked Questions
What can FlowRunner do with Autovit?
FlowRunner agents can run Create Advert, Update Advert, and Delete Advert in Autovit, plus 8 more actions.
Does connecting Autovit to FlowRunner require OAuth?
Yes. Autovit connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can Autovit trigger a FlowRunner workflow automatically?
Autovit doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Autovit
$100 in credits. No card required. Connect in minutes.