Ellipse Gradient for Header

LeanData Integration Guide

Integrate LeanData through its routing APIs and Salesforce REST or Bulk APIs to match Leads and Contacts, assign ownership, and distribute revenue orchestration outcomes.

LeanData integration options at a glance

LeanData integrations are primarily API-led and Salesforce-centric. Documented LeanData routing scenarios can be accessed through REST APIs, while Salesforce REST APIs provide access to Leads, Contacts, Accounts, Opportunities, Campaign Members, and related objects processed by LeanData. Salesforce Bulk API can support high-volume operations when appropriate, although LeanData-specific bulk behavior requires confirmation. Salesforce events, outbound messaging, or other callback mechanisms may provide selected notifications, but LeanData-specific webhook coverage is not confirmed. Martini can securely consume these APIs, expose an API for routing requests, transform payloads, apply matching rules, and orchestrate retries and reconciliation workflows.

Integration pointSupported by LeanData?Common use casesHow Martini supports it
REST APIsLimitedLeanData provides API-based routing scenarios, while Salesforce REST APIs expose the Leads, Contacts, Accounts, Opportunities, and Campaign Members processed by LeanData. Tenant-specific endpoints, request formats, and operations require confirmation.Martini can consume REST APIs, securely manage credentials, map request and response payloads, and orchestrate multi-step routing workflows.
Salesforce REST APIsYesRead and update Salesforce objects used for lead-to-account matching, ownership, territory, routing, and downstream revenue processes.Martini can call Salesforce REST endpoints, paginate results, apply transformations, and write updates with validation and retry handling.
Bulk / async / batch APIsLimitedSalesforce Bulk API can support high-volume object operations. LeanData-specific bulk processing behavior and supported routing operations must be confirmed.Martini can submit and monitor supported batch jobs, poll status, process partial failures, and reconcile results.
Webhooks / outbound callbacksLimitedLeanData-specific outbound webhook coverage is not confirmed. Salesforce outbound messaging, platform events, or other callbacks may be available depending on configuration.Martini can receive documented callback or event notifications and route them into workflows, but event coverage and delivery semantics must be validated first.
Salesforce event notificationsLimitedSalesforce event or change-notification mechanisms may support selected real-time synchronization scenarios where enabled by the customer.Martini can receive supported event inputs, retrieve the current Salesforce resource, apply idempotency checks, and distribute the result.
AuthenticationLimitedSalesforce OAuth 2.0, access and refresh tokens, profiles, permission sets, object permissions, and field-level security govern access to Salesforce-hosted LeanData data. LeanData API credentials may also be required.Martini stores OAuth credentials, client secrets, API keys, URLs, and environment-specific configuration in protected secrets and uses them in controlled workflows.
File / attachment APIsNot confirmedNo LeanData-specific file or attachment API was confirmed. Salesforce APIs may be used where the implementation requires supported file or attachment handling.Martini can process files and API payloads when a documented Salesforce integration surface is available, but no LeanData-specific file mechanism should be assumed.
Database accessNoDirect database access to LeanData-managed data is not a documented integration approach because LeanData is delivered through Salesforce.Martini should use documented LeanData or Salesforce APIs rather than attempting direct database connectivity.

How LeanData exposes data and business events

LeanData REST APIs

LeanData supports API-based routing scenarios, while Salesforce REST APIs provide access to the Salesforce objects processed by LeanData. The exact routing request, response schema, endpoint, and permissions depend on the customer tenant and selected implementation.

Martini implementation pattern

Martini implementation pattern: expose a controlled Martini API or receive an upstream request, validate the payload, call the documented LeanData or Salesforce REST endpoint, interpret the matched Account and ownership result, and return or distribute a normalized outcome.

Implementation sequence

Receive the routing request
Validate required prospect and company fields
Assign a stable idempotency key
Call the documented LeanData or Salesforce REST endpoint
Map the routing response to the canonical model
Write the result to Salesforce or the requesting application

Salesforce REST APIs

Salesforce REST APIs are a primary integration surface for Leads, Contacts, Accounts, Opportunities, Campaign Members, and related data processed by LeanData. They can support both synchronization and routing-related updates.

Martini implementation pattern

Martini implementation pattern: authenticate with Salesforce OAuth, retrieve changed objects using a reliable marker, normalize matching fields, invoke the applicable LeanData or Salesforce processing path, and update downstream systems after validating the result.

Implementation sequence

Authenticate with Salesforce OAuth 2.0
Retrieve changed Salesforce objects
Normalize email domains and company fields
Apply matching and routing business rules
Update Salesforce or downstream systems
Store the last successful timestamp or cursor

Salesforce Bulk API

Salesforce Bulk API can support high-volume object operations, although LeanData-specific bulk behavior and routing support require confirmation. It is most relevant when individual REST requests would exceed practical throughput.

Martini implementation pattern

Martini implementation pattern: prepare an approved batch, submit it through Salesforce Bulk API, poll job status, process successful and failed rows separately, and reconcile routing or ownership outcomes without duplicating requests.

Implementation sequence

Prepare a validated batch of Salesforce objects
Submit the supported Bulk API job
Poll the job until completion
Process successful and failed rows
Reconcile partial routing outcomes
Record the batch checkpoint

Salesforce events and callbacks

LeanData-specific webhooks were not confirmed. Depending on Salesforce configuration, platform events, outbound messaging, or another callback mechanism may notify external systems of selected changes or routing results.

Martini implementation pattern

Martini implementation pattern: receive only a documented Salesforce event or callback, verify its authenticity and event identity, retrieve the current resource when necessary, apply idempotency, and deliver the normalized outcome to downstream systems.

Implementation sequence

Receive the documented Salesforce notification
Verify the event identity and payload
Retrieve the current Salesforce resource if required
Check whether the event was already processed
Map the routing or ownership outcome
Acknowledge or retry according to the callback contract

Common LeanData integration patterns

Pattern 1: Submit external Leads for LeanData routing

When to use this pattern

Use this pattern when a website, marketing platform, partner application, or other external source needs LeanData or Salesforce to match a Lead to an Account and determine the appropriate owner, queue, or sales team.

Integration direction
External application
Martini
LeanData
Salesforce
Example Mapping
LeanData FieldCanonical FieldTarget Field
emailperson.emailLead.Email
companyorganization.nameLead.Company
countryorganization.countryLead.Country
sourceacquisition.sourceLead.LeadSource
Martini implementation pattern

Martini exposes a controlled API, validates required fields, normalizes email and company data, and calls the documented LeanData routing or Salesforce API path. It applies no-match and fallback-owner rules, returns a normalized routing result, and persists the request key and outcome for retries and reconciliation.

Martini capabilities used
  • APIs
  • workflows
  • data mapping
  • business rules
  • error handling

Pattern 2: Synchronize Salesforce Leads and Contacts

When to use this pattern

Use this pattern when marketing, sales, or customer-data applications need consistent Lead and Contact data together with LeanData-derived Account, ownership, or routing context.

Integration direction
Salesforce
Martini
LeanData
Marketo Engage
Example Mapping
LeanData FieldCanonical FieldTarget Field
Idperson.sourceIdlead.externalId
Emailperson.emaillead.email
AccountIdperson.accountIdlead.accountExternalId
OwnerIdassignment.ownerIdlead.ownerExternalId
Martini implementation pattern

A scheduled or event-driven Martini workflow retrieves changed Salesforce objects, normalizes matching fields, submits applicable records through the documented processing path, and updates Salesforce or marketing targets. It uses LastModifiedDate or a supported event marker, stable IDs, and retry-safe writes.

Martini capabilities used
  • workflow orchestration
  • API consumption
  • data mapping
  • incremental synchronization
  • idempotency
  • error handling

Pattern 3: Distribute routing outcomes to sales engagement

When to use this pattern

Use this pattern when routed Leads or Contacts should be enrolled in an approved Outreach or Salesloft process after ownership and eligibility have been determined.

Integration direction
Salesforce
LeanData
Martini
Outreach
Example Mapping
LeanData FieldCanonical FieldTarget Field
Lead.Idprospect.sourceIdprospect.externalId
Emailprospect.emailprospect.email
OwnerIdassignment.ownerIdprospect.ownerId
routing statusassignment.statusenrollment.status
Martini implementation pattern

Martini consumes a documented routing result or Salesforce callback, checks for an eligible owner and existing enrollment, maps the prospect to the sales engagement model, and writes only approved changes. Duplicate enrollment keys and transient target failures are handled through idempotency and retry policies.

Martini capabilities used
  • event-driven workflows
  • business rules
  • data transformation
  • API consumption
  • duplicate prevention
  • retry handling

Pattern 4: Process high-volume Account routing context

When to use this pattern

Use this pattern when Account ownership, territory, or matching attributes must be synchronized at scale with a downstream customer-data or service application.

Integration direction
Salesforce
Martini
ServiceNow
Example Mapping
LeanData FieldCanonical FieldTarget Field
Idaccount.sourceIdaccount.externalId
Nameaccount.nameaccount.name
Websiteaccount.domainaccount.domain
OwnerIdassignment.ownerIdaccount.ownerExternalId
Martini implementation pattern

Martini retrieves eligible Accounts through Salesforce REST or an approved Bulk API process, transforms ownership and territory context, and updates the downstream application in controlled batches. The workflow polls batch status, isolates partial failures, records checkpoints, and reconciles records that could not be processed.

Martini capabilities used
  • scheduled workflows
  • Bulk API orchestration
  • batch processing
  • mapping and transformation
  • checkpointing
  • reconciliation

Applications commonly integrated with LeanData

LeanData is primarily deployed within Salesforce, so adjacent integrations typically exchange prospect, account, ownership, routing, and campaign context with Salesforce and LeanData processing. The following applications represent common or conservative enterprise architecture patterns; the exact LeanData-supported workflow should be confirmed for each customer environment.

Application Scenario Direction Martini Pattern
Salesforce Salesforce is the primary platform where LeanData performs lead-to-account matching, routing, ownership, and revenue orchestration. Salesforce → Martini → LeanData Martini consumes Salesforce REST or Bulk API data, submits documented LeanData routing requests where required, maps routing results, and updates Salesforce objects with controlled retries and idempotency.
Marketo Engage Marketing-generated Leads and Campaign Members can be submitted for account matching and sales assignment, with routing outcomes returned to marketing operations. Marketo Engage → Martini → Salesforce → LeanData Martini receives or retrieves Marketo Engage data, validates and normalizes prospect fields, writes the Salesforce representation, and distributes the resulting owner or routing status back to marketing workflows.
HubSpot Inbound prospects and lifecycle data can be synchronized with Salesforce so LeanData processing can use account and ownership context. HubSpot → Martini → Salesforce → LeanData A Martini workflow consumes HubSpot data, maps contacts and company attributes to Salesforce Leads or Contacts, invokes the documented routing path, and optionally sends assignment status back to HubSpot.
Oracle Eloqua Marketing prospects and campaign information can be passed into Salesforce-based matching and sales assignment processes. Oracle Eloqua → Martini → Salesforce → LeanData Martini transforms Eloqua prospect and campaign payloads into Salesforce-compatible objects, validates required matching fields, invokes routing where applicable, and records rejected or unmatched submissions for review.
Outreach Routed Leads and Contacts can be distributed to sales engagement sequences after LeanData or Salesforce determines ownership. Salesforce → LeanData → Martini → Outreach Martini consumes routing outcomes, applies eligibility and duplicate-enrollment rules, maps owner and prospect fields to Outreach, and retries transient delivery failures without creating duplicate enrollments.
ServiceNow Account, contact, and ownership context can support consistent assignments when revenue operations and service workflows need shared customer information. Salesforce → LeanData → Martini → ServiceNow Martini consumes approved Salesforce or LeanData results, maps account and ownership context to ServiceNow records, applies field and visibility rules, and handles rejected or partially completed updates.

How to build a LeanData integration in Martini

Objective

Establish authenticated access to LeanData and Salesforce using the API surface appropriate to the use case.

Instructions in Martini

  • Confirm the LeanData API or Salesforce objects and operations required.
  • Configure Salesforce OAuth 2.0, LeanData credentials, tenant URLs, and permissions.
  • Store tokens, secrets, and environment-specific endpoints in Martini secrets or protected configuration.
  • Verify object-level permissions and field-level security for Leads, Contacts, Accounts, Opportunities, and Campaign Members.

Objective

Select the trigger that matches the required latency, volume, and delivery contract.

Instructions in Martini

  • Use a Martini API when an external system submits a routing request.
  • Use a documented Salesforce event or callback only when its coverage and delivery behavior are confirmed.
  • Use a scheduler for incremental synchronization or reconciliation.
  • Use Bulk API processing for approved high-volume Salesforce operations.

Objective

Receive or retrieve the source payload and establish a reliable processing boundary.

Instructions in Martini

  • Validate required fields and payload structure.
  • Retrieve the current Salesforce resource when an event contains only an identifier.
  • Use pagination and a last-successful timestamp, cursor, or change marker for incremental reads.
  • Assign or preserve a stable source ID and routing-request key.

Objective

Coordinate LeanData, Salesforce, and downstream calls as a maintainable Martini workflow.

Instructions in Martini

  • Call the documented LeanData or Salesforce endpoint for the selected operation.
  • Separate validation, routing, persistence, and notification stages.
  • Apply controlled concurrency and backoff for transient Salesforce or LeanData failures.
  • Capture request, response, status, and correlation identifiers.

Objective

Convert vendor payloads into a canonical model and target-specific representations.

Instructions in Martini

  • Normalize email addresses, domains, phone numbers, countries, and company names.
  • Map Lead, Contact, Account, Opportunity, Campaign Member, and routing result fields explicitly.
  • Handle optional, custom, renamed, or unavailable Salesforce fields without silently discarding required data.
  • Preserve source IDs and routing status for traceability.

Objective

Enforce matching, eligibility, ownership, and duplicate-prevention decisions before writing results.

Instructions in Martini

  • Define behavior for no-match, multiple-match, inactive-owner, and invalid-data outcomes.
  • Check whether the routing request or downstream enrollment was already processed.
  • Apply fallback queue, review, enrichment, or notification rules where appropriate.
  • Respect Salesforce validation, automation, and assignment behavior.

Common LeanData data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
LeadRepresent a prospective person or business contact for matching, routing, ownership assignment, and conversion processes.Salesforce, Marketo Engage, HubSpot, Oracle Eloqua, OutreachMartini validates and normalizes email, company, geography, and source fields, submits the Lead through the documented routing or Salesforce API path, and records the outcome.
ContactRepresent an individual associated with an Account and support matching, ownership, and downstream sales processes.Salesforce, Outreach, ServiceNow, HubSpotMartini synchronizes Contact identifiers and account relationships, applies field-level mappings, and prevents duplicate downstream updates using stable Salesforce IDs.
AccountProvide the company context used for account matching, ownership, territory, and routing decisions.Salesforce, ServiceNow, customer-data applicationsMartini retrieves or updates Account attributes, normalizes domains and company names, and distributes matched-account or assignment context to approved targets.
OpportunityRepresent a potential sales transaction whose account relationship, owner, and routing criteria may drive revenue orchestration.Salesforce, Outreach, ServiceNowMartini maps opportunity and ownership fields, applies eligibility rules, and routes approved outcomes while preserving Salesforce identifiers and processing state.
Campaign MemberAssociate a Lead or Contact with a Salesforce Campaign and provide marketing context for prioritization or routing.Salesforce, Marketo Engage, Oracle EloquaMartini synchronizes campaign context, validates related Lead or Contact references, and distributes selected routing or status changes downstream.
Routing request or routing resultSubmit an external routing request and return a matched Account, owner, queue, routing status, or error outcome.External applications, Salesforce, LeanDataMartini exposes or consumes controlled APIs, assigns a stable request key, transforms the documented schema, applies no-match and retry rules, and persists the result for reconciliation.

Authentication and security considerations

Salesforce authentication

LeanData is commonly deployed as a Salesforce-native application. Access to LeanData-managed data therefore follows Salesforce OAuth 2.0, access and refresh tokens, profiles, permission sets, object-level permissions, field-level security, and API permissions.

Credential protection

Store Salesforce tokens, LeanData API credentials, client secrets, tenant URLs, and endpoint configuration in protected Martini secrets or environment-specific configuration rather than embedding them in workflows.

Least-privilege access

  • Grant only the objects, fields, records, and API operations required by the workflow.
  • Review access to Lead, Contact, Account, and Opportunity data.
  • Use separate credentials and endpoints for development, testing, and production.
  • Avoid logging personal or commercially sensitive fields unnecessarily.

Operational considerations for LeanData integrations

Limits and throughput

Salesforce API limits apply to Salesforce access, and LeanData-specific quotas or routing limits should be confirmed with the customer subscription and documentation. Use controlled concurrency, backoff, and Bulk API evaluation for high-volume workloads.

Pagination and incremental processing

Continue through paginated Salesforce responses and persist cursors, offsets, or last-successful timestamps where supported. Define how updates, deletes, merges, ownership changes, and converted Leads are detected.

Matching and idempotency

Normalize email domains, company names, phone numbers, and country codes before routing. Use Salesforce IDs, external IDs, or deterministic request keys to prevent duplicate routing requests and downstream updates.

Schema and failure handling

  • Monitor Salesforce custom-field and LeanData routing-configuration changes.
  • Handle invalid data, no-match and multiple-match results, inactive owners, validation failures, expired tokens, and rate limits.
  • Separate partial batch failures from successful rows and reconcile them from stored checkpoints.
  • Test against Salesforce automation, validation rules, field-level security, and representative routing configurations.

Why use Martini instead of scripts or point-to-point integrations?

Centralized orchestration

Martini coordinates LeanData, Salesforce, marketing, sales engagement, and service systems in workflows rather than scattering routing logic across scripts and point-to-point connections.

Reusable integration assets

Teams can expose controlled APIs, consume documented REST endpoints, reuse mappings and validation logic, and apply consistent authentication, error handling, retries, and observability.

Adaptable business rules

Martini can normalize matching data, apply fallback and eligibility rules, preserve idempotency state, and accommodate Salesforce custom fields or tenant-specific routing behavior without changing every downstream integration.

Operational maintainability

Workflow-based checkpoints, logs, environment-specific secrets, batch reconciliation, and explicit mappings make the integration easier to monitor, test, troubleshoot, and evolve than isolated scripts.

Frequently asked questions

How can LeanData be integrated with enterprise systems?

LeanData can be integrated through documented API-based routing scenarios and Salesforce REST APIs for Leads, Contacts, Accounts, Opportunities, Campaign Members, and related data. Salesforce Bulk API may support high-volume operations, while Salesforce events, outbound messaging, or other callbacks may support selected notification scenarios. Exact endpoints, schemas, and event coverage depend on the customer environment.

Can Martini integrate with LeanData?

Yes. Martini can integrate with LeanData by consuming documented LeanData REST endpoints, calling Salesforce REST or Bulk APIs for Salesforce-hosted objects, exposing an API for external routing requests, and orchestrating supported Salesforce event or callback mechanisms. A specific tenant’s API scope and authentication requirements should be confirmed before implementation.

Do I need a connector to integrate LeanData with Martini?

No. A dedicated LeanData connector is not required. Martini can use LeanData’s documented APIs, Salesforce APIs, and supported Salesforce callbacks or event mechanisms. The appropriate integration surface depends on whether the requirement concerns LeanData routing or Salesforce object synchronization.

Is there any extra Lonti cost to integrate LeanData with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate LeanData. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from LeanData, Salesforce, cloud infrastructure, or other third-party services based on subscription, usage, and deployment model.

Which APIs or integration methods should be used for LeanData?

Use a documented LeanData API when submitting an external routing request or retrieving a LeanData-specific result. Use Salesforce REST APIs for Leads, Contacts, Accounts, Opportunities, Campaign Members, and related Salesforce data. Consider Salesforce Bulk API for high-volume processing after confirming the supported operations and LeanData behavior.

Are LeanData webhooks or event callbacks available?

LeanData-specific webhook coverage was not confirmed. A customer may use Salesforce platform events, outbound messaging, or another documented callback mechanism depending on configuration. Event coverage, authentication, delivery guarantees, and retry behavior should be validated before designing a real-time workflow.

How does synchronization and data mapping work with LeanData?

Martini can retrieve changed Salesforce objects using a supported change marker, normalize matching fields, map vendor objects to a canonical model, and write routing or ownership outcomes to downstream systems. Stable Salesforce IDs, external IDs, timestamps, cursors, and routing-request keys support incremental synchronization and duplicate prevention.

How are errors, retries, and duplicate routing requests handled?

Martini workflows can validate payloads, classify authentication, rate-limit, validation, no-match, and downstream errors, and retry transient failures with controlled backoff. Stable Salesforce IDs or external request keys support idempotency. Batch operations should isolate partial failures and retain checkpoints for reconciliation.

Related Martini documentation

APIs

Workflows

Mapping

Security

Operations

Integrate LeanData with Martini

Use Martini to connect LeanData and Salesforce routing processes with the applications that support your revenue operations. Talk with Lonti about designing a secure, maintainable integration.

EXPLORE MARTINI
BOOK A DEMO