.png)
Salesforce Financial Services Cloud Integration Guide
Salesforce Financial Services Cloud integrates with enterprise systems through Salesforce REST, SOAP, GraphQL, Bulk, event, callback, and OAuth-enabled platform APIs.
Salesforce Financial Services Cloud integration options at a glance
Salesforce Financial Services Cloud is built on Salesforce Platform and exposes REST APIs for sObjects, SOQL, SOSL, composite requests, and metadata-related operations. GraphQL supports unified queries for selected objects, while SOAP remains relevant for WSDL-based and strongly typed integrations. Bulk API 2.0 supports asynchronous queries and ingestion for large datasets. Salesforce also provides Platform Events, Change Data Capture, Pub/Sub API, Outbound Messages, and Apex callouts, although event coverage depends on configuration and object support. Martini can consume these APIs, receive selected callback traffic, orchestrate workflows, transform FSC data, manage OAuth credentials, and expose controlled REST endpoints.
| Integration point | Supported by Salesforce Financial Services Cloud? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Query and modify standard, custom, and FSC sObjects using SOQL, SOSL, composite resources, and resource-specific endpoints. | Martini can consume Salesforce REST endpoints from workflows, map responses, manage pagination and watermarks, and expose REST APIs as a controlled façade. |
| GraphQL APIs | Limited | Retrieve related Salesforce data through a unified query model where the required objects and operations are supported by the API version. | Martini can consume Salesforce GraphQL APIs and transform nested responses, while REST or Bulk APIs can handle unsupported objects or larger transfers. |
| SOAP APIs | Yes | Support Enterprise WSDL, Partner WSDL, strongly typed integrations, and legacy enterprise applications. | Martini can consume Salesforce SOAP services where WSDL-based integration is required, with REST and Bulk assessed first for new data designs. |
| Webhooks and outbound callbacks | Limited | Use Outbound Messages, Apex callouts, or related Salesforce automation to notify external endpoints for selected configured events or changes. | Martini can expose endpoints or receive webhook-style requests, validate and acknowledge them, and move processing into controlled workflows. |
| Platform Events, CDC, and Pub/Sub API | Limited | Publish or consume business events and change notifications for supported objects, with replay and delivery behavior determined by the selected mechanism. | Martini can consume supported event endpoints or receive event-facing traffic, deduplicate messages, enrich payloads, and route them to downstream systems. |
| Bulk and asynchronous APIs | Yes | Run large asynchronous queries, ingest high-volume upserts, perform initial migrations, and reconcile Accounts, Contacts, Financial Accounts, and other objects. | Martini can submit jobs, poll status, retrieve success and failure results, transform rows, and route rejected records for remediation. |
| File and attachment APIs | Yes | Create, query, and associate ContentVersion, ContentDocument, ContentDocumentLink, and legacy Attachment records where configured. | Martini can orchestrate file metadata and content transfers, associate files with Salesforce records, and apply validation and security controls. |
| Authentication | Yes | Authenticate through Connected Apps and OAuth 2.0 flows including JWT bearer, refresh-token, and supported client-credentials configurations. | Martini can store credentials, certificates, and secrets securely and use authenticated API workflows with Salesforce scopes and permissions. |
| Analytics and reporting APIs | Limited | Retrieve report metadata, report results, and analytics data for governed reporting or downstream analysis; this is not direct SQL database access. | Martini can call reporting or analytics APIs, transform results, and schedule delivery to target applications or data platforms. |
How Salesforce Financial Services Cloud exposes data and business events
Salesforce REST APIs
Salesforce REST APIs provide general-purpose access to sObjects, SOQL, SOSL, composite requests, and resource-specific operations. Their coverage makes REST the usual starting point for FSC synchronization and API-led integration, subject to object permissions, API versions, and organization-specific configuration.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates through the Salesforce Connected App, calls the required REST resource, follows pagination or next-record links, maps the response into a canonical model, and writes to the target system. The workflow stores a watermark or correlation state and classifies Salesforce errors for retry or remediation.
Implementation sequence
Salesforce GraphQL APIs
Salesforce GraphQL provides a unified query model for supported Salesforce data and can retrieve related data in a single query. Object and operation coverage varies by API version, so it is complementary to REST rather than a complete replacement.
Martini implementation pattern
Martini implementation pattern: a workflow submits a controlled GraphQL query, validates the nested response, transforms related objects into the target model, and falls back to REST or another supported API when required FSC objects are outside the GraphQL schema.
Implementation sequence
Salesforce SOAP APIs
Salesforce Enterprise and Partner WSDLs support strongly typed and legacy enterprise integrations. SOAP remains relevant where generated client bindings or an existing WSDL contract is required, although REST and Bulk should generally be assessed for new designs.
Martini implementation pattern
Martini implementation pattern: a workflow invokes the required Salesforce SOAP operation, handles XML serialization and SOAP faults, maps the typed response to the canonical model, and applies bounded retries only to transient failures.
Implementation sequence
Salesforce Bulk API 2.0
Bulk API 2.0 supports asynchronous query and ingest operations for large Salesforce datasets. It is appropriate for initial migrations, periodic reconciliation, and high-volume upserts of Accounts, Contacts, Financial Accounts, and other configured objects.
Martini implementation pattern
Martini implementation pattern: a workflow creates a bulk query or ingest job, polls status with bounded backoff, retrieves successful and failed results, transforms rows, and records rejected rows with their Salesforce error messages for remediation.
Implementation sequence
Salesforce events and callbacks
Salesforce supports Platform Events, Change Data Capture, Pub/Sub API, Outbound Messages, Apex callouts, and selected streaming mechanisms. These are configuration-dependent and should not be treated as a universal webhook for every FSC object or field change.
Martini implementation pattern
Martini implementation pattern: Martini receives supported callback traffic or consumes an event endpoint, authenticates and validates the message, deduplicates using event or record identifiers, enriches the payload through Salesforce APIs when necessary, and routes business processing asynchronously.
Implementation sequence
Common Salesforce Financial Services Cloud integration patterns
Pattern 1: Synchronize customers and households
When to use this pattern
Use this pattern when Salesforce FSC is the relationship-management system and a core banking platform, customer data platform, or marketing application needs synchronized customer and household information. It supports scheduled incremental extraction, event-assisted updates, and periodic reconciliation.
Integration direction
Example Mapping
| Salesforce Financial Services Cloud Field | Canonical Field | Target Field |
|---|---|---|
| Account.Id | customer.sourceId | customer.externalReference |
| Account.Name | customer.displayName | customer.name |
| PersonEmail | customer.email | customer.emailAddress |
| Account.ParentId | relationship.parentSourceId | customer.parentReference |
Martini implementation pattern
Martini retrieves Accounts, Person Accounts, Contacts, household relationships, and selected changes using REST, CDC, or a scheduled watermark. It normalizes identity fields, resolves parent-child relationships, validates required data, and upserts the target using Salesforce IDs or external IDs. Duplicate, permission, and validation failures are separated from transient API failures and recorded for remediation.
Martini capabilities used
- workflows
- API consumption
- scheduling
- data mapping
- business rules
- error handling
Pattern 2: Synchronize Financial Accounts and roles
When to use this pattern
Use this pattern when FSC must exchange holdings and relationship information with a core banking, wealth management, or portfolio platform. It is appropriate for configured Financial Account and Financial Account Role objects whose fields and relationships have been verified in the customer organization.
Integration direction
Example Mapping
| Salesforce Financial Services Cloud Field | Canonical Field | Target Field |
|---|---|---|
| FinancialAccount.Id | financialAccount.sourceId | account.externalReference |
| FinancialAccount.Name | financialAccount.displayName | account.name |
| FinancialAccountRole.RoleType | relationship.role | accountHolder.roleCode |
| FinancialAccountRole.FinancialAccountId | relationship.accountSourceId | accountHolder.accountReference |
Martini implementation pattern
A Martini workflow retrieves or receives Financial Account changes, resolves related Financial Account Roles and customer identifiers, applies product and ownership rules, and writes parent accounts before relationships. It uses idempotent upserts, retains Salesforce references, and routes missing parents, invalid role types, and record conflicts to an exception process.
Martini capabilities used
- workflows
- API consumption
- data mapping
- relationship orchestration
- business rules
- error handling
Pattern 3: Route service Cases across platforms
When to use this pattern
Use this pattern when Salesforce Cases need fulfillment in ServiceNow or another service application and status, assignment, resolution, or reference information must return to Salesforce. It is suitable for event-driven processing with scheduled reconciliation.
Integration direction
Example Mapping
| Salesforce Financial Services Cloud Field | Canonical Field | Target Field |
|---|---|---|
| Case.Id | serviceCase.sourceId | incident.correlationId |
| Case.Subject | serviceCase.summary | incident.shortDescription |
| Case.Status | serviceCase.status | incident.state |
| Case.Priority | serviceCase.priority | incident.urgency |
Martini implementation pattern
Martini receives a supported Salesforce event or retrieves changed Cases, validates the Case and customer references, maps statuses and priority values, and creates or updates the ServiceNow item. Returned status changes are mapped back to Salesforce. Case ID plus source version or event identifier provides idempotency, while rate limits and temporary failures use bounded retries.
Martini capabilities used
- event-driven workflows
- API consumption
- data mapping
- conditional routing
- idempotency
- retry handling
Pattern 4: Perform bulk migration and reconciliation
When to use this pattern
Use this pattern for an initial migration or high-volume reconciliation involving Accounts, Contacts, Financial Accounts, or other FSC objects. Bulk API 2.0 is preferable to one synchronous REST request per record when volume is substantial.
Integration direction
Example Mapping
| Salesforce Financial Services Cloud Field | Canonical Field | Target Field |
|---|---|---|
| Account.Id | customer.sourceId | customer.salesforceId |
| SystemModstamp | source.modifiedAt | customer.sourceModifiedAt |
| FinancialAccount.Balance | financialAccount.value | holding.currentValue |
| Contact.Email | person.email | person.emailAddress |
Martini implementation pattern
Martini submits asynchronous Bulk API jobs, polls status with backoff, retrieves successful and failed results, transforms records into the target schema, and loads the destination in controlled batches. It persists job IDs and watermarks, captures rejected rows with Salesforce errors, and runs a later reconciliation to identify missed, deleted, or changed data.
Martini capabilities used
- workflows
- Bulk API orchestration
- scheduling
- data mapping
- batch processing
- monitoring
- error handling
Applications commonly integrated with Salesforce Financial Services Cloud
Salesforce Financial Services Cloud can be integrated with adjacent Salesforce products and enterprise applications for customer engagement, analytics, service operations, workforce administration, document signing, and data platforms. The exact design depends on the customer’s Salesforce edition, licensed products, configured FSC objects, security model, and target application APIs.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce Marketing Cloud | Synchronize customer, household, consent, segmentation, campaign, and engagement data for targeted communications. | Salesforce Financial Services Cloud → Martini → Salesforce Marketing Cloud | Martini can retrieve Accounts, Person Accounts, Contacts, and consent-related data through Salesforce APIs, map the data to Marketing Cloud interfaces, apply eligibility rules, and return campaign or engagement outcomes to Salesforce with correlation and retry handling. |
| Salesforce Data Cloud | Unify customer and interaction data across Salesforce and external sources for identity resolution, segmentation, and activation. | Salesforce Financial Services Cloud → Martini → Salesforce Data Cloud | A Martini workflow can extract selected FSC objects, normalize identifiers and relationship data, deliver the mapped payload through the available Data Cloud interfaces, and coordinate status or activation results back to Salesforce. |
| Tableau | Provide governed reporting across customer, Financial Account, Opportunity, Case, and service data. | Salesforce Financial Services Cloud → Martini → Tableau | Martini can retrieve Salesforce data or report results through supported APIs, apply privacy and business filters, transform the output into the required Tableau ingestion model, and run scheduled or incremental delivery workflows. |
| ServiceNow | Coordinate Salesforce Cases with operational tasks, incidents, fulfillment, and service processes managed in ServiceNow. | Salesforce Financial Services Cloud → Martini → ServiceNow | Martini can receive Case changes or retrieve them incrementally, map Salesforce IDs and status values to ServiceNow records, route updates in both directions, and use idempotency keys and retry classification to prevent duplicate work. |
| Workday | Synchronize employee, advisor, branch, organizational, or user-related data where workforce information affects Salesforce ownership or access. | Workday → Martini → Salesforce Financial Services Cloud | Martini can retrieve approved Workday workforce and organization data, transform it into Salesforce Account, Contact, User-related, or ownership models where configured, validate required relationships, and upsert changes using controlled schedules. |
| DocuSign | Initiate and track electronic signatures for account-opening, lending, advisory, consent, and other financial documents. | Salesforce Financial Services Cloud → Martini → DocuSign | A workflow can receive a Salesforce business event, assemble a document envelope request from FSC data and file references, submit it to DocuSign, and write envelope status and signed-document references back to Salesforce. |
| Snowflake | Centralize Salesforce customer and financial-services data for enterprise analytics, regulatory reporting, and data science. | Salesforce Financial Services Cloud → Martini → Snowflake | Martini can use Salesforce Bulk API or incremental REST extraction, preserve Salesforce IDs and watermarks, transform FSC objects into analytics-oriented structures, and load Snowflake through its available ingestion interface without direct Salesforce database access. |
| MuleSoft Anypoint Platform | Coordinate Salesforce with core banking, wealth, payments, and other enterprise applications through reusable APIs. | Salesforce Financial Services Cloud → Martini → MuleSoft Anypoint Platform | Martini can consume or expose REST, SOAP, GraphQL, and event-facing interfaces, apply canonical mappings and business rules, and provide an orchestrated boundary between FSC and reusable MuleSoft APIs. |
How to build a Salesforce Financial Services Cloud integration in Martini
Objective
Establish Salesforce access with a Connected App, OAuth 2.0 flow, appropriate scopes, and an integration principal that has only the required FSC object and field permissions.
Instructions in Martini
- Create or obtain the Salesforce Connected App configuration.
- Choose an OAuth flow appropriate for the deployment, such as JWT bearer for server-to-server use.
- Store client credentials, certificates, and private keys in secure Martini configuration.
- Validate object, field-level, sharing, and record visibility permissions.
Objective
Select a trigger that matches the integration’s latency and coverage requirements without assuming that all FSC changes are available as universal webhooks.
Instructions in Martini
- Choose a scheduled workflow, REST API invocation, CDC or Platform Event consumption, or configured callback.
- Confirm the selected objects, fields, retention, replay, and delivery behavior.
- Define a reconciliation schedule for event-assisted integrations.
Objective
Retrieve the required FSC objects through REST, GraphQL, SOAP, or Bulk APIs while handling pagination, asynchronous jobs, and configured object availability.
Instructions in Martini
- Inspect the organization’s available objects and fields before finalizing mappings.
- Use SOQL filters and a stable watermark for incremental extraction.
- Follow next-record links or poll Bulk API jobs as required.
- Retrieve related records and file metadata only when the business process needs them.
Objective
Implement the end-to-end Martini workflow that coordinates Salesforce calls, enrichment, validation, target writes, and response handling.
Instructions in Martini
- Separate trigger, retrieval, transformation, target-write, and exception stages.
- Use reusable services or workflow components for common Salesforce operations.
- Preserve Salesforce IDs, external IDs, event identifiers, and correlation IDs.
- Keep long-running processing asynchronous where callback or bulk behavior requires it.
Objective
Convert Salesforce standard, FSC, custom, and managed-package fields into a canonical model and the target application’s schema.
Instructions in Martini
- Map Accounts, Contacts, Person Accounts, Financial Accounts, Roles, Cases, or other configured objects explicitly.
- Normalize dates, picklists, currencies, identifiers, and relationship references.
- Handle optional fields and organization-specific record types without assuming universal FSC schemas.
- Transform ContentVersion and related file metadata separately from business objects.
Objective
Apply validation, routing, ownership, deduplication, and parent-child sequencing rules before writing downstream data or sending updates to Salesforce.
Instructions in Martini
- Validate required fields and configured Salesforce constraints.
- Use Salesforce IDs or external IDs for correlation and idempotent upsert.
- Sequence parent objects before Financial Account Roles or other dependent relationships.
- Route duplicate, permission, validation, and data-quality failures for correction.
Common Salesforce Financial Services Cloud data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Account | Represents households, organizations, businesses, or other customer accounts. | Core banking platforms, customer data platforms, Marketing Cloud, Data Cloud, and analytics platforms. | Martini retrieves or receives Account changes, maps account and relationship identifiers, applies validation and ownership rules, and upserts using Salesforce IDs or configured external IDs. |
| Contact | Represents individual people associated with Accounts and customer relationships. | Marketing Cloud, customer data platforms, Workday-related processes, and service applications. | Martini normalizes identity and consent fields, validates Account relationships, applies duplicate rules, and synchronizes Contacts incrementally or through bulk jobs. |
| Person Account | Represents an individual customer where Person Accounts are enabled. | Customer data platforms, marketing systems, wealth platforms, and analytics stores. | Martini detects the organization’s Person Account configuration, maps person-specific fields separately from business Accounts, and preserves Salesforce identifiers and relationship data. |
| Financial Account | Represents deposits, investment accounts, or other financial products and holdings. | Core banking, wealth management, portfolio, regulatory reporting, and analytics platforms. | Martini retrieves configured Financial Account fields, applies product and ownership rules, orders parent-child processing, and upserts records with external correlation keys. |
| Financial Account Role | Represents the relationship between a person or organization and a Financial Account. | Core banking, wealth management, customer data, and entitlement systems. | Martini resolves both sides of the relationship, validates role types, sequences writes after parent objects, and handles duplicate or conflicting relationships explicitly. |
| Opportunity | Represents prospective products, services, referrals, or financial business. | Salesforce Marketing Cloud, financial origination platforms, analytics, and document-signing systems. | Martini maps stages, products, amounts, owners, and references, applies routing rules, and synchronizes changes with idempotent upsert behavior. |
Authentication and security considerations
OAuth and Connected Apps
Salesforce integrations generally use a Connected App with OAuth 2.0. JWT bearer authentication is often appropriate for server-to-server workflows, while refresh tokens and other supported flows depend on Connected App policies and organizational requirements.
Least-privilege access
API authentication does not automatically grant access to every FSC object or field. Profiles, permission sets, field-level security, sharing rules, record visibility, record types, validation rules, and licensed FSC capabilities all affect integration behavior.
Credential protection
- Store Salesforce client credentials, refresh tokens, certificates, and private keys in secure Martini configuration.
- Use separate integration principals and environments where appropriate.
- Protect financial data and Salesforce file content according to organizational retention, encryption, and access policies.
Operational considerations for Salesforce Financial Services Cloud integrations
Limits and pagination
Salesforce applies org-level API limits and may impose concurrency or processing limits. REST responses can be paginated through nextRecordsUrl, while Bulk API jobs are asynchronous. Martini workflows should avoid repeated full extracts, use bounded polling, and prefer composite or bulk operations where appropriate.
Incremental synchronization
Use stable watermarks such as SystemModstamp or LastModifiedDate, supported change events, and periodic reconciliation. Persist job IDs, event identifiers, watermarks, and target correlation keys so a workflow can resume safely.
Idempotency and retries
Use Salesforce IDs or external IDs for upsert correlation and account for duplicate event delivery. Retry rate-limit, temporary availability, and selected concurrency failures with bounded backoff, but route validation, permission, malformed-query, and duplicate errors for correction.
Schema and event behavior
FSC object availability, fields, managed packages, event coverage, replay behavior, and delivery guarantees vary by organization. Inspect metadata, test in a sandbox, version mappings, and define acknowledgement, replay, dead-letter, and ordering behavior before production deployment.
Why use Martini instead of scripts or point-to-point integrations?
Orchestrated integration logic
Martini coordinates Salesforce API calls, event handling, target writes, enrichment, validation, and business rules in maintainable workflows rather than scattering logic across scripts or point-to-point interfaces.
Flexible API coverage
Because FSC is built on Salesforce Platform, implementations may require REST, GraphQL, SOAP, Bulk, event, callback, and file APIs. Martini can consume these standards-based interfaces and expose controlled REST APIs when applications or Salesforce callouts need a stable façade.
Operational control
- Centralize mappings, transformations, credentials, correlation, and error handling.
- Support scheduled, event-driven, synchronous, asynchronous, and bulk processing patterns.
- Reuse integration assets while adapting to organization-specific FSC objects, fields, permissions, and managed packages.
- Monitor workflow outcomes and route failed records for controlled remediation.
Frequently asked questions
Salesforce Financial Services Cloud can be integrated through Salesforce REST APIs, GraphQL for supported objects, SOAP APIs, Bulk API 2.0, reporting and analytics APIs, and configured event or callback mechanisms such as Change Data Capture, Platform Events, Pub/Sub API, Outbound Messages, and Apex callouts. OAuth 2.0 through a Connected App is the normal authentication model.
Yes. Martini can integrate with Salesforce Financial Services Cloud by consuming its REST, GraphQL, SOAP, and Bulk APIs, receiving supported event or callback traffic, exposing REST endpoints for Salesforce callouts, and orchestrating mappings, business rules, retries, and target-system writes.
No dedicated Salesforce Financial Services Cloud connector is required. Martini can use Salesforce’s confirmed native APIs, event mechanisms, callbacks, files, and OAuth authentication through standards-based workflows and APIs.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Salesforce Financial Services Cloud. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Salesforce, cloud infrastructure, or other third-party systems based on licensing, usage, and deployment model.
REST is the general-purpose starting point for most FSC integrations. Bulk API 2.0 is better for large asynchronous loads and extracts, GraphQL is useful for supported related-data queries, and SOAP remains relevant for existing WSDL-based or strongly typed integrations. The selected API should reflect object coverage, volume, latency, and compatibility requirements.
Salesforce supports Platform Events, Change Data Capture, Pub/Sub API, Outbound Messages, Apex callouts, and selected streaming mechanisms. Coverage is configuration-dependent and varies by object, event type, retention, replay behavior, and delivery model; these mechanisms should not be described as a universal webhook for every FSC change.
Martini can use scheduled REST or Bulk API extraction with SystemModstamp or LastModifiedDate watermarks, supported change events, or a combination of events and periodic reconciliation. Workflows preserve Salesforce IDs and external IDs, apply mappings and business rules, and use idempotent upserts to reduce duplicates.
Martini maps Salesforce and FSC objects into canonical and target models, validates required fields, and applies configurable business rules. Transient rate-limit, concurrency, or availability failures can use bounded backoff and retries, while validation, permission, malformed-query, and duplicate errors are captured for correction. Salesforce IDs, external IDs, event identifiers, and correlation IDs support idempotency.
Related Martini documentation
APIs
Transformation
Plan your Salesforce Financial Services Cloud integration
Connect Salesforce Financial Services Cloud to enterprise applications with Martini workflows, APIs, secure authentication, data mapping, event handling, and operational controls.