AutoCerto
AutoCerto is the NicoApp for integration with the AutoCerto system (integracao.autocerto.com), used by vehicle dealerships for inventory management. With it, your flow queries brands, models and vehicles in the inventory.
Note
Available in the NicoApps tab. Integration base: official AutoCerto API (integracao.autocerto.com).
How to obtain the access credentials
The app asks for only two fields during installation: Username and Password. According to AutoCerto's official Swagger, the API uses OAuth2 with the "password" flow (endpoint /oauth/token): the system exchanges that username and password for an access token automatically — you do not need to generate or paste a token manually, only provide the login.
Attention
AutoCerto does not publish a self-service guide for generating the integration username/password. Everything indicates that it is the same login used in the store's system, but confirm with AutoCerto the official path and whether the store's contract includes API access.
Recommended path:
- Contact AutoCerto support (suporte@autocerto.com) or the store's account/sales manager and request the release/confirmation of access to the integration API (integracao.autocerto.com), stating that the use will be through an external integration (chatbot).
- Ask explicitly whether the username and password used to log in to the AutoCerto system (the same as the panel at admin.autocerto.com) work for the API, or whether the store needs a separate integration credential.
- Before configuring it in NicoChat, you can test the credentials directly in the Swagger documentation (integracao.autocerto.com/swagger/ui/index), using the authorization button (OAuth2/padlock) with the username and password — if it authenticates and lists the inventory there, the same credentials work in the app.
- If the store has more than one branch linked to the same login, use the optional Unidade field in the actions to filter/route by store.
Note
The credential is validated on the first action executed. If an action fails with an authorization error, check the Username and the Password in the app configuration before suspecting another problem.
Limitations
Attention
The request limit (rate limit) is not publicly disclosed by AutoCerto. Check with support or the account manager whether there is any request cap for the store's contract before sizing high-volume flows.
- Large inventories: the response of Obter Estoque and Obter Placa is limited to about 20,000 characters before it is saved to the flow variable (NicoChat's own protection against huge payloads, not an AutoCerto limit). In stores with a very large inventory, use the filters (brand, model, year, price, branch) so that you do not lose vehicles in the response.
- Criar Lead uses a different format from the other actions: the request body is sent as
application/x-www-form-urlencoded, not as JSON. This is transparent for whoever uses the app, but it is relevant when debugging payload errors. - Código do Interesse is a fixed AutoCerto list (0KM, Seminovos, Compras, Pós-Venda) with non-sequential numbering (1, 2, 8, 9, 10) — the "skipped" numbers are like that at the source, it is not an app error.
What the NicoApp does
Action
What it does
Main inputs
Outputs
Obter Estoque
Lists the store's vehicle inventory, with optional filters
Unidade (if there is more than one store), ID da Marca, ID do Modelo, Ano mínimo/máximo, Preço mínimo/máximo — all optional
Veículos Encontrados (JSON/array)
Obter Marcas
Lists the vehicle brands and their IDs
— (no input)
Marcas (JSON/array)
Obter Modelos
Lists the models of a brand and their IDs
Código da Marca (required)
Modelos (JSON/array)
Obter Versões
Lists the versions of a model/year and their IDs
Código do Modelo, Ano do Modelo (both required)
Versões (JSON/array)
Obter Veículo
Brings all the details of a vehicle by ID
ID do Veículo (required)
Marca, Modelo, Versão, Ano Fabricação/Modelo, Km, Cor, Combustível, Câmbio, Preço, Preço Classificados, Placa, Portas, Renavam, Chassi, Observação, URL do Vídeo, Opcionais (array), Fotos (array)
Obter Placa
Searches for a vehicle by license plate and already returns the complete details (chains with Obter Veículo)
Placa (required)
ID do Veículo + the same complete fields as Obter Veículo
Criar Lead
Registers a lead/interested party in AutoCerto
Mídia (required); Unidade, Interesse, ID do Veículo, Nome, E-mail, Telefone, Telefone2, Mensagem, Descrição do Veículo, Placa, CPF, CEP (optional)
ID do Lead
Tips and notes
- Obter Placa chains with Obter Veículo: internally, the action searches for the vehicle in the inventory filtering by license plate, takes the returned ID and already calls Obter Veículo automatically — that is why the response brings the vehicle's complete record, not just the ID. There is no need to call the two actions manually.
- Criar Lead sends form-urlencoded, not JSON: if you are going to investigate a payload error in this specific action, remember that the body goes as
application/x-www-form-urlencoded(with the correspondingContent-Typeheader), unlike the query actions. - Dynamic selects: the Unidade and Mídia fields load their options directly from the AutoCerto account after you install the app with the credentials.
- Marcas, Modelos and Versões reuse the same return variable: read the result of each action right afterwards, before chaining the next call (Marcas → Modelos → Versões), so that you do not overwrite data that still needs to be read.
- Error handling: when AutoCerto refuses an operation (e.g.: nonexistent license plate, vehicle not found, invalid credential), the action fails and returns the real error message from the API — use the block's error path to handle it in the flow.
- Unidade is optional in most actions: only fill it in when the credential has access to more than one store.