Skip to main content
Autodoc is a Brazilian construction-industry platform for document management. Its GD4 module controls the legal and fiscal documentation of workers (colaboradores) and suppliers (fornecedores) across construction sites (obras) — required documents, analysis status, expirations and site-access blocking. Nekt extracts this data through the official GD4 API.

​
Configuring Autodoc as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Autodoc 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 User: The username of the API user of your GD4 account. An administrator can create it in the GD4 interface, under Autodoc > Usuário API. Module permissions for the API user are configured per construtora under Autodoc > Construtora — streams the user has no permission for are skipped with a warning.
  • API Password: The password of that API user.
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.
The per-worker document streams (colaboradores_historico and the four colaboradores_documentos_* streams) and per-supplier document streams (fornecedores_documentos*) make one API call per worker/supplier, so syncs get slower as your workforce grows. Select only the ones you need.
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: the Autodoc API does not expose update timestamps, so all streams are extracted as FULL_TABLE — every run fetches the current state of the data.
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 Autodoc and their corresponding fields.
Some detailed document payloads are not fully documented by the Autodoc API, so they are delivered as JSON strings (columns historico, documentos and fornecedor on the per-worker/per-supplier streams). You can parse them with SQL JSON functions in your Queries.
Workers registered in GD4, with their documentation status. Full table.Key Fields:
  • id - Unique identifier of the worker in GD4
  • nome - Full name of the worker
  • cpf - CPF (Brazilian individual taxpayer ID) of the worker
  • data_nascimento - Birth date of the worker
  • data_admissao - Date the worker was hired
  • data_cadastro - Date the worker was registered in GD4
  • funcao - Job function (role) of the worker
  • cargos_servicos - Positions/services assigned to the worker
  • responsavel - Name of the supplier (employer) responsible for the worker
  • relationships - Details of the responsible supplier (JSON object)
  • obras - Construction sites the worker is linked to
  • analise_documento - Document analysis status for the worker
  • status_colaborador - Current documentation status of the worker
  • estado_residencia / cidade_residencia - Where the worker lives
  • facial_cadastrada - Whether facial recognition is enrolled for turnstile access
Individual history entries of each worker (admissions, transfers, events). Full table. One API call per worker.Key Fields:
  • colaborador_id - Identifier of the worker this history entry belongs to
  • historico - History entry of the worker as returned by GD4 (JSON object)
Documents required from each worker, split by requirement type: one-time (único), monthly (mensal), termination (encerramento) and transfer (transferência). Full table. One API call per worker per stream.Key Fields:
  • colaborador_id - Identifier of the worker the documents belong to
  • documentos - Document entry with status, due dates and occurrences (JSON object)
Suppliers (contractors) monitored in GD4, with documentation status. Full table.Key Fields:
  • id - Unique identifier of the supplier in GD4
  • nome_fantasia - Trade name of the supplier
  • razao_social - Legal name of the supplier
  • cnpj - CNPJ (Brazilian company taxpayer ID) of the supplier
  • categoria - Category of the supplier
  • colaboradores - Number of workers linked to the supplier
  • status_fornecedor - Current documentation status of the supplier
  • data_uploads - Date of the last document upload by the supplier
  • data_analise - Date of the last document analysis for the supplier
Documents and documentation summary of each supplier, plus the per-type listings (único, mensal, encerramento). Full table. One API call per supplier per stream.Key Fields:
  • fornecedor_id - Identifier of the supplier
  • fornecedor - Documentation summary and document list of the supplier (JSON object, summary stream)
  • documentos - Document entry with status, due dates and occurrences (JSON object, per-type streams)
Administrative supplier registry with contacts, hiring relation and hierarchy. Full table.Key Fields:
  • id - Unique identifier of the supplier in GD4
  • cnpj - CNPJ of the supplier
  • razao_social / nome_fantasia - Legal and trade names of the supplier
  • data_vinculo - Date the supplier was linked to the builder
  • codigo_fornecedor - Internal code of the supplier
  • colaboradores_vinculados - Number of workers linked to the supplier
  • contato / telefone / email - Contact information of the supplier
  • relacao_contratacao - Hiring relation of the supplier
  • fornecedor_pai - Parent supplier when subcontracted
Construction sites managed in GD4. Full table.Key Fields:
  • id - Unique identifier of the construction site
  • nome - Name of the construction site
  • endereco - Address of the construction site
  • cei - CEI/CNO registration number of the construction site
  • descricao - Description of the construction site
  • bloqueado - Whether the construction site is blocked
  • catracas - Turnstiles installed at the site (JSON array of objects)
GD4 platform users of the builder account. Full table.Key Fields:
  • id - Unique identifier of the user
  • usuario - Username (login) of the user
  • bloqueado - Whether the user is blocked
  • usuario_colaborador - Worker linked to the user account, when applicable
  • perfil - Permission profile assigned to the user
Job functions (roles) configured in GD4. Full table.Key Fields:
  • id - Unique identifier of the job function
  • nome - Name of the job function
  • codigo - Numeric code of the job function
  • uuid - UUID of the job function
  • documentos_vinculados - Documents required for the job function (JSON array of objects)
  • funcao_vinculada - Linked job function, when applicable
Positions/services configured in GD4. Full table.Key Fields:
  • id - Unique identifier of the position/service
  • nome - Name of the position/service
  • bloqueado - Whether the position/service is blocked
  • funcao - Job functions linked to the position/service (JSON array of objects)
  • data_cadastro - Date the position/service was registered
  • usuario - User who registered the position/service (JSON object)
Document type definitions (requirement rules) configured in GD4 for workers and suppliers. Full table.Key Fields:
  • id - Unique identifier of the document type
  • nome - Name of the document type
  • vencimento - Expiration rule of the document type
  • tipo_exigencia - Requirement type of the document (e.g. mensal, único)
  • peso - Weight of the document in the supplier score (supplier documents)
  • criterio_exigencia - Requirement criterion (supplier documents)
  • obras - Construction sites the requirement applies to (supplier documents)
Permission profiles and document analysis profiles configured in GD4. Full table.Key Fields:
  • id - Unique identifier of the profile
  • nome - Name of the profile
If you have any questions about the connector, feel free to reach out to us — we are happy to help you get your data flowing!