Skip to content

Stacksync × Supabase Miami: AI-Native OperationsOct 13Reserve your spot

New

Stacksync MCP is here. Give Claude, Cursor, and any MCP client governed access to your syncs, workflows, and connections.

Set up MCP
CRM · Two-way sync platform

Salesforce connector for two-way sync.

Keep Salesforce and your business systems aligned with Stacksync. Sync writable standard objects and writable custom objects within the connector’s object and field requirements, with two-way sync for eligible records.

Set this up from Claude or ChatGPT
  • Configure field mappings and sync direction
  • Inspect and resolve record errors in one dashboard
Setup guide: how Stacksync connects to Salesforce

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Record types

Salesforce objects and coverage.

Start with the records your workflow needs. Object-specific permissions and operation limits are shown alongside the available coverage.

Writable standard objects (subject to detection mode)
Check object and field eligibility in the setup guide.
Writable custom objects (subject to detection mode)
Check object and field eligibility in the setup guide.

Read the Salesforce object and setup guide

Connection setup

Salesforce connection requirements.

Check the account access and change-detection requirements for your environment. Your system administrator can help confirm permissions before the first sync.

Connection method
REST, SOAP, and Bulk APIs
Account access
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
How changes are detected
Stacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used. Confirm the selected mode for each object.

Sync directions

  • Read data Documented
  • Write data Documented
SalesforceStacksync setup guide
Setup prerequisites for your administrator
  • Authorize a Salesforce user with API access. Check whether the selected objects can use Apex triggers or require polling.
  • Test in a sandbox and make the intended objects and fields visible to the connected user.

Documentation checked September 15, 2026.

Setup guides and technical references

Integration design

Match records and fields for your Salesforce integration.

Choose the owner of customer details, qualification, and commercial status separately. A customer update, a won deal, and an approved order represent different business decisions.

Use your account’s actual field names when applying these matching and dependency checks.

Explore record matching and field-mapping checks
SalesforceSource record IDKeep the account and record type
Record matchingSource ID ↔ destination IDLink the same record across systems
Selected destinationDestination record IDPreserve its local key and rules
Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.
Match the same record in both systems
Keep the Salesforce record ID separate from the destination’s own key. Define an external matching rule for existing data and test account/contact relationships before enabling writes.
Load related records in the right order
Resolve required parent and lookup records for the chosen standard or custom object. Confirm writable fields independently of the object’s presence in the Salesforce platform.

Mapping checks by record type

Accounts

Confirm object support with Stacksync

Identity
Retain the source company ID and the destination customer/company ID. Separate legal entities, subsidiaries, and business units; a shared name or web domain is insufficient.
Fields to consider
Source record ID · Legal or display name · Business-unit reference · Lifecycle status
Related records to resolve first
Resolve parent organizations, business units, and currency references before dependent transactions.
Test before going live
Use two organizations with similar names and one with multiple business units. Verify that an update reaches the intended entity only.

Contacts

Confirm object support with Stacksync

Identity
Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key.
Fields to consider
Source person ID · Display name · Email address · Organization reference · Consent state
Related records to resolve first
Resolve the organization relationship and any owner or consent references required by the destination.
Test before going live
Test an email change, two records sharing an email, and a person associated with multiple organizations.

Leads

Confirm object support with Stacksync

Identity
Retain the lead ID and record its relationship to any converted contact or company.
Fields to consider
Source lead ID · Qualification status · Owner reference · Conversion reference
Related records to resolve first
Resolve owner and campaign references and decide how conversion changes the identity relationship.
Test before going live
Convert a test lead after the first load and verify that it does not create a duplicate person or orphan its activity.

Opportunities

Confirm object support with Stacksync

Identity
Keep the opportunity/deal ID separate from any later order or invoice ID.
Fields to consider
Source deal ID · Stage · Amount and currency · Expected close date · Company reference
Related records to resolve first
Map the customer and sales pipeline before the opportunity; map stage values deliberately.
Test before going live
Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.

Products and Price Books

Confirm object support with Stacksync

Identity
Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
Fields to consider
Source product ID · SKU or variant reference · Description · Unit of measure · Price-list reference
Related records to resolve first
Resolve units, variants, categories, and applicable price lists before order lines.
Test before going live
Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.

Cases

Confirm object support with Stacksync

Identity
Retain the ticket ID and distinguish parent tickets, follow-ups, and merged cases.
Fields to consider
Source ticket ID · Requester reference · Status · Priority · Assigned team
Related records to resolve first
Resolve requester, organization, team, and status references before ticket updates.
Test before going live
Test a merged ticket, a private note, a reopened case, and an attachment with restricted access.

Download the field-mapping workbook (CSV) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer.

Setup and validation

Validate the Salesforce integration in four steps.

A changed contact detail updates the existing person; a sales-state change reaches only the downstream process approved to act on it.

View the four setup tests and expected results

  1. Confirm the intended Salesforce account and grant

    Use the documented setup with the intended account and environment. Check that the authorizing user can grant access to the selected objects; test reauthorization without changing the mapped record identity.

    Expected result: The connection reaches the intended account, and the integration owner can renew or revoke the grant through the agreed procedure.

  2. Test the selected object in its actual capture mode

    In a sandbox, create and update an eligible object under the connected user. Confirm whether the connector uses Apex triggers or incremental polling for that object.

    Expected result: The expected record and field changes are captured in the configured mode; formula and read-only fields have separate handling.

  3. Test writes in the directions you need

    Select one eligible Salesforce object and writable field. Test the required create/update direction, an invalid value, and a repeated delivery. Check object-specific restrictions before enabling the return path.

    Expected result: The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair.

  4. Test recovery and name the support owner

    Interrupt a non-production transfer, restore the connection, and reconcile the selected Salesforce records. When using Stacksync’s Retry to sync action, check the latest source value: the retry re-reads current source state rather than replaying an immutable historical event.

    Expected result: The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors.

Use the production-readiness checklist to record test results, assign support owners, and agree on when to go live.

Troubleshooting

Troubleshoot your Salesforce integration.

Diagnose record matching, delayed changes, and rejected operations
One object updates while another stays unchanged
Compare API access, user visibility, field permissions, and detection-mode eligibility. A non-triggerable object cannot use the trigger path.
The first load looks correct but later results differ
Stacksync uses Apex triggers where permitted, or regular incremental polling when triggers cannot be used. Confirm the selected mode for each object. Measure the original source change, its capture, and the destination observation separately. Confirm whether the affected object is incremental, historical-only, or subject to a special refresh cycle.
One operation succeeds while another is rejected
Check the specific Salesforce object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available.

Review retry, replay, and recovery behavior before repeating an operation that may already have succeeded.

Review your Salesforce workflow with an engineer

Salesforce integration guides

FAQ

Salesforce connector FAQ

How should I plan an integration with Salesforce?

Object eligibility depends on the connected user and the configured trigger or polling mode. Stacksync supports two-way sync for eligible objects. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

Can the Salesforce connector write changes back?

Stacksync supports reads and writes for eligible Salesforce objects. Check the selected fields, account permissions, and the other system’s connector. In a sandbox, create and update an eligible object under the connected user. Confirm whether the connector uses Apex triggers or incremental polling for that object.

Which identifiers should I preserve for Salesforce data?

Keep the Salesforce record ID separate from the destination’s own key. Define an external matching rule for existing data and test account/contact relationships before enabling writes.

Which related records should I load first for Salesforce?

Resolve required parent and lookup records for the chosen standard or custom object. Confirm writable fields independently of the object’s presence in the Salesforce platform.

What should I check if Salesforce data is missing or delayed?

Compare API access, user visibility, field permissions, and detection-mode eligibility. A non-triggerable object cannot use the trigger path.

What will we cover in a Salesforce integration demo?

Start with one workflow and a sample record from Accounts, Contacts and Leads. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document.

Consulting on Salesforce?

Turn one-off Salesforce integration projects into a managed service clients renew.

Recurring integration revenue Become a partner

AI assistant

Set up Salesforce from Claude or ChatGPT

Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste.

1. Add the Stacksync MCP server

Server URL

https://mcp.stacksync.com/mcp

In Claude

  1. Open Customize → Connectors, select + Add, then Add custom connector.
  2. Name it Stacksync and enter https://mcp.stacksync.com/mcp.
  3. Select Connect, sign in to Stacksync and choose your workspace.

In ChatGPT

  1. Open Settings → Apps → Advanced settings and turn on Developer mode.
  2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth.
  3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat.
Set up Codex or Claude Code

Codex

codex mcp add stacksync --url https://mcp.stacksync.com/mcp
codex mcp login stacksync

Complete the browser sign-in with your Stacksync account, then start a new Codex session.

Claude Code

claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp

Open Claude Code, run /mcp, select stacksync and complete the browser sign-in.

Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet.

Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: setup steps in the docs.

2. Ask your assistant

Create a sync between my Salesforce and another app or database.

Also from the same chat

You can also ask for workflows and AI agents (Genies) that use Salesforce. The assistant checks what each app supports, for example:

  • “Build a workflow that messages our team in Slack when a Salesforce record changes.”
  • “Create a Genie that answers questions about our Salesforce data in Slack.”

What happens next

  • Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat.
  • Gives you a secure sign-in link for each app it connects; you open it and sign in to that app.
  • Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first.

New to Stacksync? Create an account first, then sign in from your assistant.

AI assistant setup

Use Salesforce through Stacksync MCP.

Explore capabilities and setup →

Explore Salesforce connections

Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair.

285 integration guides

CRM · 47

ERP · 44

Database · 49

Data warehouse · 30

Business productivity · 40

Accounting and finance · 17

AI · 5

Analytics · 7

Communications · 6

E-commerce · 8

Human resources · 13

Marketing · 9

Security and identity · 6

Storage · 4

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2SSH TunnellingSSL certificatesIP WhitelistingVPN gatewayVPC peeringand more
Coworkers laughing in front of a laptop in a casual office setting

Connect the systems your business runs on.
Build your next workflow with Stacksync.

Book a demo Get started