Real-time
Two-way sync
Changes in Pigment or Salesforce instantly reflect in both systems. No stale data, no manual imports.
Accounting and finance ⇄ CRM
Pigment to Salesforce integration — real-time, two-way sync
Keep Pigment and Salesforce in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
- SOC 2 and 6 other compliance frameworks
- POC with real engineers in minutes
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
Why teams connect Pigment and Salesforce
Sync customers, invoices, and payment status between Pigment and Salesforce in real time, so sales sees the money and finance sees the relationship.
Finance and sales describe the same customers in different systems. Salesforce knows the relationship: who the contacts are and what is in motion with the account. Pigment knows the money: what was invoiced, what was paid, what is overdue. When the two are connected only by exports, each side works partly blind.
Stacksync links Dimension lists, Tables, Scenarios, Data imports in Pigment to Contacts, Leads, Opportunities, Cases in Salesforce with bi-directional, real-time sync. New customers, updated billing details, invoice status, and payment activity move in whichever direction you configure, field by field, with conflicts resolved by rules you set. The result is one version of each customer, visible from both sides.
Common use cases
- 01 Export approved budgets and forecasts back to a warehouse or Postgres for downstream reporting.
- 02 Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
- 03 Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.
- 04 Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
Common sync patterns
Where Salesforce tracks deals: closed-won creates the finance record
A won opportunity creates or updates the customer in Pigment with the right billing details, so invoicing starts without re-keying.
Payment status on the account
Invoice and payment status from Pigment appears on the account in Salesforce, so reps see overdue balances before they promise the next order.
Billing detail changes flow back
When a contact or address is corrected in Salesforce, Pigment gets the update before the next invoice goes out.
What you can sync between Pigment and Salesforce
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| Pigment objects | Salesforce objects | How this pairing syncs | |
|---|---|---|---|
| Users and permissions Access controls governing which model areas a sync can touch | Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. | Users and permissions is specific to Pigment and Accounts to Salesforce — each maps to any object or custom field on the other side. | |
| Applications Planning models organized by domain such as finance, sales, or workforce | Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | Applications is specific to Pigment and Contacts to Salesforce — each maps to any object or custom field on the other side. | |
| Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | Metrics is specific to Pigment and Leads to Salesforce — each maps to any object or custom field on the other side. | |
| Dimension lists Master data like accounts, products, or employees that metrics are sliced by | Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. | Dimension lists is specific to Pigment and Opportunities to Salesforce — each maps to any object or custom field on the other side. | |
| Tables Row-based transactional data loaded into models from source systems | Cases Support records; synced with help desk tools or internal databases for escalation workflows. | Tables is specific to Pigment and Cases to Salesforce — each maps to any object or custom field on the other side. | |
| Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Campaigns Marketing membership data; read out for attribution analysis in the warehouse. | Scenarios is specific to Pigment and Campaigns to Salesforce — each maps to any object or custom field on the other side. |
How changes propagate between Pigment and Salesforce
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
Pigment Salesforce Interval-based propagation
DetectionStacksync polls Pigment for changes on an incremental schedule, reading only records changed since the previous pass. No change feed.
DeliveryEach detected change is written to Salesforce through its API, with automatic retries and rate-limit backoff.
Salesforce Pigment Sub-second propagation
DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).
DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Pigment: Subject to the platform's API rate limits.
- Salesforce: Daily API request allocations vary by edition and license count.
What ships with Pigment ⇄ Salesforce
Connect Pigment and Salesforce for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Pigment–Salesforce connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Pigment or Salesforce data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
At scale
Event queues
Handle millions of events per minute without losing a single Pigment or Salesforce record.
Observability
Monitoring
Track your Pigment ⇄ Salesforce sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Pigment and Salesforce.
How the Pigment and Salesforce connectors work
Pigment
- Integration surface
- REST-based import and export API
- Authentication
- API keys, issued separately for import and export
- Change detection
- no change feed; syncs run scheduled imports and exports
- Capabilities
- read · write
- Rate limits
- subject to the platform's API rate limits
Salesforce
- Integration surface
- REST, SOAP, and Bulk APIs
- Authentication
- 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
- Change detection
- Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
- Capabilities
- read · write · CDC
- Rate limits
- Daily API request allocations vary by edition and license count.
How it works
How to connect Pigment to Salesforce — three steps, no code
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
- 01
Connect your apps
Authenticate Pigment and Salesforce with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pigment
connected
Salesforce
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Pigment and Salesforce objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
objects · Pigment ⇄ SalesforceCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Pigment SalesforceCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Pigment and Salesforce integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Pigment and Salesforce: authenticate both systems, choose the objects to sync (such as Pigment's Users and permissions and Applications), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Pigment and Salesforce: Where Salesforce tracks deals: closed-won creates the finance record; Payment status on the account; Billing detail changes flow back. A won opportunity creates or updates the customer in Pigment with the right billing details, so invoicing starts without re-keying.
-
Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Salesforce: REST, SOAP, and Bulk APIs. Authentication: 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. Stacksync manages authentication, retries, and rate limits on both sides.
-
Pigment: Pigment's model is multidimensional: metrics are sliced by dimension lists, so inbound records must map to those dimensions rather than flat columns. Salesforce: Change Data Capture publishes create, update, delete, and undelete events on per-object channels, giving near-real-time change feeds without polling. Stacksync's field mapping accounts for these differences between Pigment and Salesforce without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Pigment and Salesforce records are not retained after a sync operation.
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.
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 442 integrations available for Pigment and Salesforce.
Popular · 7 of 442
-
Pigment ⇄ Seismic -
Pigment ⇄ Xactly -
Pigment ⇄ Gong -
Salesforce ⇄ Chargebee -
Salesforce ⇄ Hyperline -
Salesforce ⇄ QuickBooks -
Salesforce ⇄ Stripe
No integrations match .
