Real-time
Two-way sync
Changes in Drift or Pigment instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Accounting and finance
Drift to Pigment integration — real-time, two-way sync
Keep Drift and Pigment 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 Drift and Pigment
Sync customers, invoices, and payment status between Pigment and Drift in real time, so sales sees the money and finance sees the relationship.
Finance and sales describe the same customers in different systems. Drift 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 Scenarios, Data imports, Users and permissions, Applications in Pigment to Users, Playbooks, Meetings, Contacts in Drift 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 Keep dimension lists such as departments and cost centers consistent with master data in the ERP.
- 02 Sync headcount and compensation data from an HRIS into workforce planning models.
- 03 Archive historical Drift conversation and contact data into a warehouse ahead of a platform migration.
- 04 Sync Drift-captured contacts into the CRM so chat-sourced leads enter standard sales workflows immediately.
Common sync patterns
Collections with context
Finance sees the account owner and relationship history from Drift when chasing a balance, and sales sees that the chase is happening.
Where Drift 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 Drift, so reps see overdue balances before they promise the next order.
What you can sync between Drift and Pigment
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.
| Drift objects | Pigment objects | How this pairing syncs | |
|---|---|---|---|
| Messages Individual messages within a conversation, used for transcript and intent analysis. | Scenarios Versions such as budget, forecast, and actuals that give exported figures their context | Messages is specific to Drift and Scenarios to Pigment — each maps to any object or custom field on the other side. | |
| Accounts Company records used for account-based routing and targeting. | Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model | Accounts is specific to Drift and Data imports to Pigment — each maps to any object or custom field on the other side. | |
| Users Agents and sales reps who own conversations and meetings. | Users and permissions Access controls governing which model areas a sync can touch | Users is specific to Drift and Users and permissions to Pigment — each maps to any object or custom field on the other side. | |
| Playbooks Bot flows that generate conversations and qualify visitors. | Applications Planning models organized by domain such as finance, sales, or workforce | Playbooks is specific to Drift and Applications to Pigment — each maps to any object or custom field on the other side. | |
| Meetings Meetings booked through Drift, synced to CRM as sales activities. | Metrics Multidimensional values holding plans and actuals; the main target for inbound data | Meetings is specific to Drift and Metrics to Pigment — each maps to any object or custom field on the other side. | |
| Contacts Visitor and lead records created or matched from chat identities; the main CRM-sync object. | Dimension lists Master data like accounts, products, or employees that metrics are sliced by | Contacts is specific to Drift and Dimension lists to Pigment — each maps to any object or custom field on the other side. |
How changes propagate between Drift and Pigment
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.
Drift Pigment Sub-second propagation
DetectionDrift notifies Stacksync of record changes through webhook events. Webhook events for new conversations, messages, and contact changes.
DeliveryEach detected change is written to Pigment through its API, with automatic retries and rate-limit backoff.
Pigment Drift 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 Drift through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Drift: Subject to the platform's API rate limits.
- Pigment: Subject to the platform's API rate limits.
What ships with Drift ⇄ Pigment
Connect Drift and Pigment for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Drift–Pigment connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Drift or Pigment 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 Drift or Pigment record.
Observability
Monitoring
Track your Drift ⇄ Pigment sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Drift and Pigment.
How the Drift and Pigment connectors work
Drift
- Integration surface
- REST API
- Authentication
- OAuth 2.0 via apps registered on the Drift developer platform
- Change detection
- Webhook events for new conversations, messages, and contact changes; polling for backfills
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
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
How it works
How to connect Drift to Pigment — 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 Drift and Pigment with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Drift
connected
Pigment
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Drift and Pigment 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 · Drift ⇄ PigmentCustomers 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.
Drift PigmentCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Drift and Pigment integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Drift and Pigment: authenticate both systems, choose the objects to sync (such as Drift's Messages and Accounts), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Pigment: Actuals typically flow in from source systems on a schedule while plans and forecasts are edited inside Pigment, making it primarily a data destination. Drift: Salesloft acquired Drift in 2024, and the standalone Drift platform has since been placed on a sunset path; teams should confirm current API availability and migration timelines with Salesloft before building new integrations. Stacksync's field mapping accounts for these differences between Drift and Pigment 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 Drift and Pigment records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Drift and Pigment connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Drift–Pigment integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Drift and Pigment. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Drift: Webhook events for new conversations, messages, and contact changes; polling for backfills. On Pigment: No change feed; syncs run scheduled imports and exports. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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
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 188 integrations available for Drift and Pigment.
Popular · 3 of 188
No integrations match .
