Connector

Customer data without the export step

CRM data usually reaches an analyst as a spreadsheet somebody exported, at which point it is stale, ungoverned and full of personal data nobody classified. The CRM connector removes that step.

How it works

Records land as datasets

Contacts, accounts, opportunities and activities become profiled datasets in the catalogue.

PII flagged immediately

CRM data is mostly personal data. Those columns are detected at ingest so classification happens before the data spreads.

Refreshable

Put it in a flow and the extract stays current, instead of ageing from the moment it was taken.

Joinable

Once landed, CRM records join to your other datasets on matched keys with the match quality reported.

What happens after it lands

Once rows are in the catalogue, the connector that produced them stops mattering. The dataset is profiled, can be cleaned, modelled, put in a flow, governed and published exactly like every other dataset — which means switching how data arrives never means rebuilding what happens to it afterwards.

Questions about this connector

Does connecting a CRM modify records in it?

No. The connector reads.

How is personal data handled?

Columns that look like personal data are flagged on arrival for a classification decision, and policies can then restrict what may be done with them.

Can I limit which fields come across?

Yes — select the objects and fields you need rather than mirroring the whole CRM.

See it on your own data

DataLens is in private beta. Bring a file, a database or an API and work through the whole lifecycle in one sitting.

Request beta access