Dievio
Key points
- Inspect the actual Salesforce schema and integration permissions.
- Map available source fields under conservative identity and overwrite rules.
- Reconcile destination outcomes without restarting successful retrieval.
Syncing Dievio records into Salesforce requires an application-owned mapping and recovery process. Confirm the source operation, review the records and write only the Salesforce changes the workflow is authorized to make.
API access does not establish a native connector or automatic data verification. Keep source retrieval, identity review, Salesforce updates and campaign activation as separate stages.
Inspect the target Salesforce organisation
Choose the object and action before mapping fields. Creating a Lead, updating a Contact and associating an Account are different tasks. Confirm API access, the integration user's permissions and the chosen authentication method under current Salesforce guidance.
Inspect the actual field definitions, required values, picklists, length constraints and validation rules. The Salesforce describe reference explains the metadata available for objects and fields.
- Name the owner of the integration and failed-record queue.
- Document create, update and conflict-review behavior.
- Protect reviewed manual values and established lifecycle fields.
- Use a controlled Salesforce test environment where available.
Map actual source fields rather than generic aliases
Dievio public-search records appear in preview_data. The following examples use available source fields; coverage varies, and your destination organisation may require additional decisions.
| Source field | Possible Lead target | Review rule |
|---|---|---|
first_name | FirstName | Map when present and suitable |
last_name | LastName | Review missing names under the organisation's rules |
work_email | Email | Protect trusted values; availability is not mailbox validation |
mobile_phone | An approved phone field | Check format and intended use |
job_title | Title | Preserve qualifiers and handle length conflicts |
company | Company | Confirm the intended company association |
linkedin_url | A configured custom field | Use the actual API name and retain identity uncertainty |
If only a full name is available, do not assume a whitespace split correctly identifies given and family names. Preserve the raw value and use a defined, reviewable fallback.
Resolve identity before choosing an update
Define accepted identifiers and ambiguity handling. Email and profile URLs can support matching without being universal immutable person keys. Keep candidate matches separate from confirmed identity decisions.
Do not automatically merge records or replace a company association because a fuzzy-name result looks similar. Review Salesforce duplicate and matching rules alongside application behavior.
When appropriate, your integration can maintain a stable application-assigned external reference. Salesforce documents upsert using an external ID; the configured field and identifier semantics must be designed explicitly.
DievioYour workflow. Powered by Dievio.
Bring B2B contact search and LinkedIn enrichment into the tools you already use.
Explore Dievio APISearch contacts · Enrich profiles · Export results
{
"job_titles": ["Founder"],
"max_results": 10
}Apply field ownership and null rules
Specify who may update each field and what omission, null and deliberate clearing mean. An incoming value should not overwrite a reviewed manual correction merely because the import ran later.
Use the mapping workflow for source observations, normalized values and approved changes.
Persist before writing to Salesforce
- Store the supported source request and successful response.
- Validate required fields and resolve identity.
- Construct approved changes under the current mapping version.
- Write a bounded destination operation.
- Inspect the documented response and any record-level failures.
- Reconcile applied, excluded and unresolved outcomes.
Recover a failed destination write from stored results when appropriate. Repeating paid source retrieval can add cost without correcting a Salesforce validation error.
Choose the schedule from the decision deadline
Your application can run a scheduled job or emit an event after a reviewed result is ready. Neither establishes a native Dievio webhook feed or an immutable incremental change stream.
Use the relay guide for application delivery and the CRM sync guide for the shared architecture.
Test the resulting Salesforce records
Check missing names, unknown picklist values, protected edits, ambiguous matches, repeated events and partial writes. Verify the actual object, field values and owner after delivery rather than relying only on a successful request status.
Report accepted source records, applied updates and unresolved cases separately. Keep source and Salesforce credentials out of logs, and retain enough controlled evidence to correct a mistaken update.
