Two-way sync
Changes in Salesforce or Tinybird instantly reflect in both systems. No stale data, no manual imports.
Keep Salesforce and Tinybird in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
The CRM feeds the warehouse and the warehouse should feed the CRM: relationship data flows one way, and computed scores, segments, and customer context flow back. Most teams build the first half as a batch pipeline and never quite get to the second.
Stacksync does both with one connection. Custom Objects, Accounts, Contacts, Leads from Salesforce land in Tinybird as live tables, updated within seconds, and columns computed in Tinybird write back to fields in Salesforce. There is no separate ETL and reverse-ETL stack to stitch together and no jobs to babysit.
Deduplication and normalization done in Tinybird can be written back, so warehouse-side cleanup actually fixes the CRM.
Accounts, contacts, and activity from Salesforce are queryable in Tinybird moments after they change, so dashboards stop lagging the reality they describe.
Lead scores, churn risk, or usage segments computed in Tinybird appear as fields in Salesforce, where the people working accounts actually see them.
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.
| Salesforce objects | Tinybird objects | How this pairing syncs | |
|---|---|---|---|
| Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | Materialized Views Pipes materialized into new Data Sources for pre-aggregation at ingest time. | Contacts is specific to Salesforce and Materialized Views to Tinybird — each maps to any object or custom field on the other side. | |
| Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | Workspaces Project boundary that scopes Data Sources, Pipes, and tokens for a sync. | Leads is specific to Salesforce and Workspaces to Tinybird — each maps to any object or custom field on the other side. | |
| Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. | Tokens Scoped credentials that control read and append rights per resource. | Opportunities is specific to Salesforce and Tokens to Tinybird — each maps to any object or custom field on the other side. | |
| Cases Support records; synced with help desk tools or internal databases for escalation workflows. | Data Sources ClickHouse-backed tables that receive ingested rows; the write target for syncs into Tinybird. | Cases is specific to Salesforce and Data Sources to Tinybird — each maps to any object or custom field on the other side. | |
| Campaigns Marketing membership data; read out for attribution analysis in the warehouse. | Pipes Chained SQL nodes that transform Data Sources into query-ready results. | Campaigns is specific to Salesforce and Pipes to Tinybird — each maps to any object or custom field on the other side. | |
| Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. | API Endpoints Published Pipe outputs exposed as parameterized HTTP queries; the main read surface. | Tasks and Events is specific to Salesforce and API Endpoints to Tinybird — each maps to any object or custom field on the other side. |
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.
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 applied to Tinybird as a row-level write, with types converted between the two schemas.
DetectionStacksync polls Tinybird for changes on an incremental schedule, reading only records changed since the previous pass. Append-oriented ingestion.
DeliveryEach detected change is written to Salesforce through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Salesforce–Tinybird connection.
Changes in Salesforce or Tinybird instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Salesforce or Tinybird data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Salesforce or Tinybird record.
Track your Salesforce ⇄ Tinybird sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Salesforce and Tinybird.
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.
Authenticate Salesforce and Tinybird with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Salesforce and Tinybird 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Salesforce and Tinybird: authenticate both systems, choose the objects to sync (such as Salesforce's Contacts and Leads), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes — Stacksync ships production-grade connectors for both Salesforce and Tinybird. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Salesforce: Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting). On Tinybird: Append-oriented ingestion; reads are pulled by querying published endpoints, no outbound CDC. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Salesforce side: Custom Objects, Accounts, Contacts, Leads, plus custom fields where Salesforce exposes them. On the Tinybird side: Pipes, API Endpoints, Materialized Views, Workspaces. Stacksync auto-detects both schemas and converts types between the two systems.
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 Salesforce and Tinybird: Cleanup that sticks; CRM analytics on live data; Scores and segments back on the record. Deduplication and normalization done in Tinybird can be written back, so warehouse-side cleanup actually fixes the CRM.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 392 integrations available for Salesforce and Tinybird.