Skip to main content
CV CRM is a customer relationship management system designed specifically for Brazilian businesses. It provides tools for managing customer data, sales pipelines, and business relationships, helping companies organize and optimize their customer interactions and sales processes.

Configuring CV CRM as a Source

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

1. Add account access

You’ll need to authorize Nekt to access your CV CRM data. The following configurations are available:
  • Email: the email address used to authenticate against the API service. This should be a valid email address with enough permissions to access the CV CRM data you want to extract. The email should be in the format user@example.com.
  • API token: the authentication token required to access the API service. Please check this documentation to find more information about how to generate the token.
  • Company subdomain: the subdomain identifier for your company account. For example, if your CRM URL is https://mycompany.cvcrm.com.br, then your company subdomain would be mycompany.
  • Start date: the date from which you want to begin synchronizing data. This defines the earliest point in time for historical extraction. Any data created or modified before this date will not be included in the synchronization.
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). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
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 CV CRM and their corresponding key fields:
Stream name: leads.Endpoint:
  • /cvdw/leads
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idleadStringLead identifier
idsituacaoStringSituation identifier
situacaoStringSituation description
submotivo_cancelamentoStringCancellation sub-reason
Stream name: additional_fields.Endpoint:
  • /cvdw/campos_adicionais
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idcampoStringField identifier
campo_nomeStringField name
idfuncionalidadeStringFeature identifier
Stream name: sales.Endpoint:
  • /cvdw/vendas
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idreservaStringReservation identifier
data_reservaStringReservation date
data_vendaStringSale date
Stream name: reservas.Endpoint:
  • /cvdw/reservas
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idreservaStringReservation identifier
codigointernoStringInternal code
numero_vendaStringSale number
Stream name: reservas_flags.Endpoint:
  • /cvdw/reservas/registros/flags
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idreservaStringReservation identifier
data_criacao_reservaStringReservation creation date
empreendimentoStringEnterprise/Project name
Stream name: pre_cadastros.Endpoint:
  • /cvdw/precadastros
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idprecadastroStringPre-registration identifier
codigointernoStringInternal code
idsituacaoStringSituation identifier
Stream name: leads_visitas.Endpoint:
  • /cvdw/leads/visitas
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idtarefaStringTask identifier
data_cadStringRegistration date
dataStringDate
Stream name: corretores.Endpoint:
  • /cvdw/corretores
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
ativo_loginBooleanLogin active status
idcorretorStringBroker identifier
idimobiliariaStringReal estate identifier
Stream name: imobiliarias.Endpoint:
  • /cvdw/imobiliarias
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
ativo_painelBooleanPanel active status
idimobiliariaStringReal estate identifier
data_cadStringRegistration date
Stream name: pessoas.Endpoint:
  • /cvdw/pessoas
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idpessoaStringPerson identifier
idpessoa_intStringInternal person identifier
idpessoa_legadoStringLegacy person identifier
Stream name: empreendimentos.Endpoint:
  • /cadastros/empreendimentos
Sync Strategy:
  • Full table (no replication key configured)
  • Primary key(s): idempreendimento
Key Fields:
FieldTypeDescription
idempreendimentoStringEnterprise/Project identifier
idempreendimento_intStringInternal enterprise/project identifier
referencia_externaStringExternal reference
nomeStringName
regiaoStringRegion
cidadeStringCity
Stream name: campanhas_ativacao.Endpoint:
  • /cvdw/campanhas_ativacao
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idcampanha_leadStringLead campaign identifier
idcampanhaStringCampaign identifier
campanha_nomeStringCampaign name
Stream name: unidades.Endpoint:
  • /cvdw/unidades
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
idempreendimentoStringEnterprise/Project identifier
idempreendimento_intStringInternal enterprise/project identifier
nome_empreendimentoStringEnterprise/Project name
idtipo_empreendimentoStringEnterprise/Project type identifier
Stream name: distratos.Endpoint:
  • /cvdw/distratos
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idreservaStringReservation identifier
aprovadaBooleanApproved status
data_cadStringRegistration date
Stream name: leads_interacoes.Endpoint:
  • /cvdw/leads/interacoes
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idinteracaoStringInteraction identifier
idleadStringLead identifier
data_cadStringRegistration date
Stream name: leads_tarefas.Endpoint:
  • /cvdw/leads/tarefas
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idtarefaStringTask identifier
data_cadStringRegistration date
dataStringDate
Stream name: leads_historico_situacoes.Endpoint:
  • /cvdw/leads/historico/situacoes
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idhistoricoStringHistory identifier
idleadStringLead identifier
data_cadStringRegistration date
Stream name: comissoes.Endpoint:
  • /cvdw/comissoes
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idcomissaoStringCommission identifier
situacaoStringSituation
idsituacaoStringSituation identifier
Stream name: atendimentos.Endpoint:
  • /cvdw/atendimentos
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idatendimentoStringService/Attendance identifier
protocoloStringProtocol
data_cadStringRegistration date
Stream name: assistencias.Endpoint:
  • /cvdw/assistencias
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idassistenciaStringAssistance identifier
idclienteStringCustomer identifier
documento_clienteStringCustomer document
Stream name: leads_conversoes.Endpoint:
  • /cvdw/leads/conversoes
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idlead_conversaoStringLead conversion identifier
idleadStringLead identifier
nomeStringName
Stream name: repasses.Endpoint:
  • /cvdw/repasses
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
data_cadStringRegistration date
ultima_atualizacaoStringLast update
data_modificacao_situacaoStringSituation modification date
idreservaStringReservation identifier
Stream name: leads_workflow_tempo.Endpoint:
  • /cvdw/leads/workflow/tempo
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idtempoStringTime identifier
idleadStringLead identifier
idsituacaoStringSituation identifier
Stream name: reservas_condicoes.Endpoint:
  • /cvdw/reservas/condicoes
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idreservascondicoesStringReservation conditions identifier
idreservaStringReservation identifier
serieStringSeries
Stream name: reservas_contratos.Endpoint:
  • /cvdw/reservas/contratos
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idreservacontratoStringReservation contract identifier
idreservaStringReservation identifier
data_cadStringRegistration date
Stream name: reservas_sienge.Endpoint:
  • /cvdw/reservas/sienge
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
data_cadStringRegistration date
idsienge_reservaStringSienge reservation identifier
idreservaStringReservation identifier
Stream name: leads_corretores.Endpoint:
  • /cvdw/leads/corretores
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): idlead, idcorretor, data_cad
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idleadStringLead identifier
data_cadStringRegistration date
idcorretorStringBroker identifier
Stream name: unidades_situacao.Endpoint:
  • /cvdw/unidades/situacao
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
idempreendimentoStringEnterprise/Project identifier
idempreendimento_intStringInternal enterprise/project identifier
nome_empreendimentoStringEnterprise/Project name
idtipo_empreendimentoStringEnterprise/Project type identifier
Stream name: pre_cadastros_historico_situacoes.Endpoint:
  • /cvdw/precadastro/historico/situacoes
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idhistoricoStringHistory identifier
idprecadastroStringPre-registration identifier
data_cadStringRegistration date
Stream name: distribuicao_leads.Endpoint:
  • /cvdw/distribuicao/leads
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
id_logStringLog identifier
recebido_emStringReceived at
id_filaStringQueue identifier
Stream name: empreendimentos_cvbot.Endpoint:
  • /cvbot/empreendimentos
Sync Strategy:
  • Full table (no replication key configured)
  • Primary key(s): idempreendimento
Key Fields:
FieldTypeDescription
idempreendimentoStringEnterprise identifier
nomeStringName
enderecoStringAddress
cidadeStringCity
estadoStringState
data_entregaStringDelivery date
Stream name: empreendimentos_unidades_cvbot.Endpoint:
  • /cvbot/empreendimentos/{idempreendimento}/unidades
Sync Strategy:
  • Full table (no replication key configured)
  • Primary key(s): idunidade
Key Fields:
FieldTypeDescription
idunidadeStringUnit identifier
nomeStringName
area_privativaStringPrivate area
vagas_garagemStringGarage spaces
andarStringFloor
area_comumStringCommon area
Stream name: pessoas_profissional.Endpoint:
  • /cvdw/pessoas/profissional
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idpessoaStringPerson identifier
idpessoa_intStringInternal person identifier
trabalho_nome_empresaStringWork company name
Stream name: tipologias_unidades.Endpoint:
  • /configuracoes/tipologias-unidades
Sync Strategy:
  • Full table (no replication key configured)
  • Primary key(s): idtipologia
Key Fields:
FieldTypeDescription
idtipologiaStringTypology identifier
nomeStringName
ativo_painelBooleanPanel active status
data_cadStringRegistration date
Stream name: reservas_associados.Endpoint:
  • /cvdw/reservas/associados
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idassociadoStringAssociate identifier
idreservaStringReservation identifier
idpessoaStringPerson identifier
Stream name: usuarios_administrativos.Endpoint:
  • /cvdw/usuarios_administrativos
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idusuarioStringUser identifier
ativo_painelBooleanPanel active status
tipo_loginStringLogin type
Stream name: pesquisas.Endpoint:
  • /cvdw/pesquisas
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idpesquisaStringSurvey identifier
data_inicioStringStart date
data_fimStringEnd date
Stream name: pesquisas_perguntas.Endpoint:
  • /cvdw/pesquisas/perguntas
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idpesquisa_perguntaStringSurvey question identifier
idperguntaStringQuestion identifier
nome_perguntaStringQuestion name
Stream name: pesquisas_respostas.Endpoint:
  • /cvdw/pesquisas/respostas
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
data_respostaStringResponse date
idpesquisaStringSurvey identifier
idperguntaStringQuestion identifier
Stream name: assistencias_itens.Endpoint:
  • /cvdw/assistencias/itens
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idassistencia_itemStringAssistance item identifier
idassistenciaStringAssistance identifier
itemStringItem
Stream name: assistencias_workflow_tempo.Endpoint:
  • /cvdw/assistencias/workflow/tempo
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idtempoStringTime identifier
idassistenciaStringAssistance identifier
idsituacaoStringSituation identifier
Stream name: assistencias_itens_workflow_tempo.Endpoint:
  • /cvdw/assistencias/itens/workflow/tempo
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idtempoStringTime identifier
idassistenciaStringAssistance identifier
idsituacaoStringSituation identifier
Stream name: assistencias_visitas_workflow_tempo.Endpoint:
  • /cvdw/assistencias/visitas/workflow/tempo
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idtempoStringTime identifier
idvisitaStringVisit identifier
idsituacaoStringSituation identifier
Stream name: atendimentos_respostas.Endpoint:
  • /cvdw/atendimentos/respostas
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idrespostaStringResponse identifier
idatendimentoStringService/Attendance identifier
idusuarioStringUser identifier
Stream name: atendimentos_workflow_tempo.Endpoint:
  • /cvdw/atendimentos/workflow/tempo
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idtempoStringTime identifier
idatendimentoStringService/Attendance identifier
idsituacaoStringSituation identifier
Stream name: atendimentos_interacoes.Endpoint:
  • /cvdw/atendimentos/interacoes
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idinteracaoStringInteraction identifier
idatendimentoStringService/Attendance identifier
idusuarioStringUser identifier
Stream name: unidades_precos.Endpoint:
  • /cvdw/unidades/precos
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idunidadeStringUnit identifier
unidadeStringUnit
valor_avaliacaoStringEvaluation value
Stream name: atendimentos_times.Endpoint:
  • /cvdw/atendimentos/times
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idtimeStringTeam identifier
idgestorStringManager identifier
gestorStringManager name
Stream name: atendimentos_times_integrantes.Endpoint:
  • /cvdw/atendimentos/times/integrantes
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idintegranteStringMember identifier
idtimeStringTeam identifier
timeStringTeam name
Stream name: atendimentos_tarefas.Endpoint:
  • /cvdw/atendimentos/tarefas
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idatendimentoStringService/Attendance identifier
protocoloStringProtocol
data_cadStringRegistration date
Stream name: reservas_workflow_tempo.Endpoint:
  • /cvdw/reservas/workflow/tempo
Sync Strategy:
  • Incremental replication key: referencia_data
  • Primary key(s): referencia
Key Fields:
FieldTypeDescription
referenciaStringReference ID
referencia_dataStringDate reference for incremental sync
ativoBooleanActive status
idtempoStringTime identifier
idreservaStringReservation identifier
idsituacaoStringSituation identifier
situacaoStringSituation name
siglaStringAcronym
tempoStringTime
data_cadStringRegistration date

Implementation Notes

Empty Response Handling

The CV CRM connector safely handles 204 No Content and empty body responses from the API, particularly on paginated endpoints. This prevents data pipeline failures when specific data streams or pages return no data during the synchronization window.

Skills for agents

Download CV CRM skills file

CV CRM connector documentation as plain markdown, for use in AI agent contexts.