Setup

Data enrichment (generic connector)

Point to your enrichment provider (Clearbit, Apollo, Hunter, People Data Labs, whichever you prefer) and automatically fill in the empty fields of companies and contacts.

Data enrichment is a generic, neutral connector: you use the account of whichever enrichment provider you prefer (Clearbit, Apollo, Hunter, People Data Labs, among others). You provide the provider's address, how to authenticate and a field mapping; the CRM queries the provider and fills in only the empty fields of the record. There is no cost on our side, and the account and billing belong to the provider you choose.

The connector starts inert: nothing happens until you configure it. The API key you provide is stored encrypted and is never displayed back.

Prerequisites

An account with an enrichment provider (Clearbit, Apollo, Hunter, People Data Labs or another) with an active API key and sufficient credits/plan.
That provider's API documentation at hand: the endpoint, the authentication header (e.g., Authorization: Bearer, or X-Api-Key) and the structure of the response JSON (to build the mapping).
In Sellio, administrator access to save the connector in Settings → Integrations.

Step by step at the provider

Sign in to your enrichment provider's dashboard and find the API/Developers area.
Generate (or copy) an API key.
Note the query endpoint by domain and/or email and the exact format of the required authentication header. Each provider has its own.

How to configure

Open Settings → Integrations and go to the "Data enrichment" card.
Endpoint (URL): paste the provider's address using the {domain} and/or {email} placeholders. The CRM replaces {domain} with the record's domain (from the website/domain or the email domain) and {email} with the record's email.
Authentication header and Prefix: enter the header name (e.g., Authorization) and the value prefix (e.g., "Bearer " with a space). Some providers use their own header, such as X-Api-Key, with no prefix.
API key: paste your provider key. It is stored encrypted.
Field mapping: each row links a path in the provider's response (on the left) to a CRM field (on the right). Add as many rows as you need.
Save the connector. Then, on a Company or Contact detail, use the "Enrich" button.

How to build the mapping

The left side is the path to the value inside the provider's JSON response, using dots to go down levels (and numbers for list positions). The right side is the api_name of the CRM field that will receive the value. Only EMPTY fields are filled: data already present in the record is never overwritten.

Example: Endpoint: https://api.provider.com/v1/company?domain={domain} • Header: Authorization • Prefix: "Bearer " • Mapping: company.name → name, company.metrics.employees → employee_count, company.location.country → country

💡 If the response returns a list, use the index: contacts.0.email takes the email of the first item. Values that are whole objects or lists are ignored; only simple values (text, number) fit in a field.

To enrich, the record must have at least a website/domain or an email, since that is where the {domain}/{email} of the query comes from. Companies usually have a website; contacts and leads, an email.

No provider of your own: system mode and simulated mode

If you do not configure your own provider, the "Enrich" button is still available. When Sellio has a system provider enabled, each enrichment fills the standard firmographic fields (employees, revenue, industry, technologies, LinkedIn, country) and uses 1 credit per record, billed transparently on your invoice. With no provider at all, the CRM uses simulated sample data (no cost), handy to try the flow. The Integrations card shows which mode is active.

Bulk and automatic enrichment

Bulk: select several records in the Companies, Contacts or Leads list and click "Enrich" in the action bar. The CRM enriches them all at once, filling only the empty fields.
Automatic on creation: in Settings → Integrations, turn on "Automatically enrich on record creation". Every new company, contact or lead gets its empty fields filled as soon as it is created.
Daily catch-up: an automatic routine reviews recent records of tenants with the option on and completes whatever is pending, within a daily limit. Reprocessing the same record never charges twice.

How to test

Open a Company that has a website/domain (or a Contact with an email) whose fields are partially empty.
Click "Enrich".
Check that the empty fields were filled according to your mapping. Compare with the provider's expected response to validate the JSON paths.

Troubleshooting

401/403 from the provider: wrong/expired API key or incorrect authentication header. Check the header name and prefix (e.g., "Bearer " with a space) and re-paste the key.
Nothing is filled in: check that the mapping paths match the provider's actual JSON (use dots to go down levels and indices for lists, e.g., contacts.0.email). Only simple values (text/number) fit in a field; whole objects/lists are ignored.
Some fields are not updated even when the provider returns data: enrichment only writes to EMPTY fields. If a field already has a value, it is preserved by design.
"Enrich" button does nothing: confirm the record has a website/domain or email (the query uses {domain}/{email}) and that the endpoint uses those placeholders.
404/invalid endpoint: review the endpoint URL and whether the provider expects a domain or email in the query.

Open this article inside the system →