Skip to main content
Mobuss Construção is a Brazilian construction-management platform covering the whole construction lifecycle: technical assistance / warranty service (assistência técnica), inspection and handover (vistoria & entrega), quality forms, workforce time-tracking (apontamento) and workplace safety (EPI). Nekt extracts this data through the Mobuss integration API.

​
Configuring Mobuss Construção as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Mobuss Construção option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

The following configurations are required:
  • API Token: The access token for the Mobuss integration API. It is issued by the Mobuss team — request it through your Mobuss account manager or support.
  • Company ID: (Optional) The company identifier issued by the Mobuss team together with the token. Some services require it; leave it empty if the Mobuss team did not provide one.
  • Start Date: (Optional) The earliest date from which records will be synced for incremental streams (service requests, time entries, PPE deliveries, handover controls). Defaults to 2025-01-01.
  • Quality service IDs: (Optional, advanced) The legacy-system service IDs (idLegado) used by the quality forms stream. Leave empty to skip that stream.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

Below you’ll find all available data streams from Mobuss Construção and their corresponding fields.
The Mobuss API only lists service requests closed or resolved on a given date — there is no endpoint listing every service request. Open requests are therefore not extracted.
Construction projects (obras) of the company linked to the token. Full table.Key Fields:
  • id - Unique identifier of the construction project in Mobuss Construção
  • nome - Name of the construction project
  • id_legado - Identifier of the project in the customer’s legacy/ERP system
  • locais - Units/locations of the project (JSON array of objects)
Units/locations (locais) of each construction project. Full table.Key Fields:
  • id_obra - Identifier of the construction project the location belongs to
  • id - Unique identifier of the location
  • cod_local - Code of the location
  • nome - Name of the location
  • hierarquia - Hierarchical path of the location within the project
  • ordem - Order of the location within its hierarchy level
  • data_habitese - Occupancy-permit (habite-se) date
  • id_legado - Identifier of the location in the customer’s legacy system
Technical-assistance service requests closed (encerradas) on each day. Incremental by closing date.Key Fields:
  • id - Unique identifier of the service request
  • numero_solicitacao - Human-readable number of the request
  • nome_solicitante / telefone_solicitante / email_solicitante - Requester contact details
  • nome_empreendimento - Name of the development/project
  • nome_unidade - Name of the unit/location
  • nome_cliente - Name of the client
  • area_comum - Whether the request refers to a common area
  • data_encerramento - Date/time the request was closed (replication key)
Technical-assistance service requests resolved (resolvidas) on each day. Incremental by resolution date. Same fields as the closed-requests stream, with data_resolucao as the replication key.
Full detail of service requests closed or resolved on each day, including visits. Incremental.Key Fields:
  • id - Unique identifier of the service request
  • numero - Human-readable number of the request
  • situacao - Current status
  • data_abertura - Date/time the request was opened
  • obra / unidade - Project and unit of the request
  • data_resolucao / data_encerramento - Resolution and closing dates
  • diagnostico - Diagnosis of the request
  • procedencia - Whether the request was deemed valid
  • descricao - Description of the request
  • visitas - Visits (vistoria/reparo) of the request (JSON array of objects)
Comments of each service request extracted by the detail stream.Key Fields:
  • id_solicitacao - Identifier of the service request
  • id_legado - Identifier of the comment in the legacy system
  • descricao - Text of the comment
  • data_inclusao / usuario_inclusao - Creation date and author
  • data_alteracao / usuario_alteracao - Last change date and author
Workforce time entries (apontamentos) per project period, filtered by change date. Incremental in 30-day windows.Key Fields:
  • id_apontamento - Unique identifier of the time entry
  • id_obra / nome_obra - Project of the time-tracking period
  • id_periodo / data_inicio_periodo / data_fim_periodo - Time-tracking period
  • data_inicio_apontamento / data_fim_apontamento - Start/end of the entry
  • nome_servico / tipo_servico - Service worked on
  • nome_local - Location worked on
  • nome_colaborador / cpf_colaborador / nome_funcao_colaborador - Worker details
  • nome_empreiteira_colaborador - Worker’s contractor company
  • valor_funcao_colaborador - Value of the worker’s role
  • retrabalho_apontamento - Whether the entry refers to rework
  • anexos - Attachments (JSON array of objects)
PPE (EPI) deliveries and write-offs per worker, by delivery date. Incremental in 30-day windows.Key Fields:
  • record_hash - Deterministic hash used as primary key (the API exposes no id)
  • dsc_nome_colaborador_recebeu_epi / num_cpf_colaborador_recebeu_epi - Worker who received the PPE
  • dsc_tipo_epi / dsc_modelo_epi / dsc_categoria_epi - PPE type, model and category
  • num_ca_epi - Approval-certificate (CA) number
  • data_entrega_epi / num_qtd_entregue_epi - Delivery date and quantity
  • data_baixa_epi / dsc_natureza_baixa_epi - Write-off date and nature
  • dsc_razao_social_fabricante_epi / num_cnpj_fabricante_epi - Manufacturer details
Inspection & handover controls whose stage was completed on each day, per stage type (Construção, Inspeção Final, Vistoria do Cliente, Entrega das Chaves). Incremental.Key Fields:
  • id - Unique identifier of the handover control
  • tipo_etapa / nome_etapa - Stage type queried
  • data_conclusao_etapa - Day the stage was completed (replication key)
  • nome_local / codigo_local - Location of the control
  • nome_cliente - Client of the location, with phone and e-mail fields
  • nome_obra / id_legado_obra - Project of the control
Quality forms and their non-conformities per configured service. Only extracted when the Quality service IDs setting is filled. Incremental in 30-day windows by change date.Key Fields:
  • id_legado_servico / tipo_servico - Service the forms belong to
  • id_formulario_realizado - Unique identifier of the filled-in form
  • nome / tipo / categoria - Form name, type and category
  • data_realizacao - Date the form was filled in
  • situacao_formulario / situacao_verificacao - Form and verification status
  • ncs - Non-conformities linked to the form (JSON array of objects)
  • locais - Locations linked to the form (JSON array of objects)