Real-time
Two-way sync
Changes in Freshworks CRM or Treasuredata instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Analytics
Freshworks CRM to Treasuredata integration — real-time, two-way sync
Keep Freshworks CRM and Treasuredata 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 Freshworks CRM and Treasuredata
Put live Freshworks CRM data behind every dashboard and cohort in Treasuredata, and write the segments and scores Treasuredata computes back onto the Freshworks CRM record — one connection, not a nightly export.
Treasuredata turns data into dashboards, cohorts, and metrics; Freshworks CRM is where customers, contacts, deals, and activity actually live and change. The two meet wherever a number is really about a specific account, segment, or stage — yet most teams feed the CRM into analytics as a nightly extract or a hand-maintained connector, so the reporting lags the business and can't be sliced by the customers and segments that matter.
Stacksync syncs Lists, Notes, Contacts, Accounts from Freshworks CRM into Treasuredata field by field and within seconds, so every dashboard and cohort runs on current records instead of a stale copy. Because the connection runs both ways, the cohorts, scores, and metrics computed in Treasuredata write back to fields in Freshworks CRM, landing where the people working accounts can see them. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Common use cases
- 01 Write CRM and product-usage records into TD Tables so they become source tables feeding parent-segment unification.
- 02 Push Predictive Segment propensity scores from TD onto customer records in an operational database or CRM for prioritization and lead routing.
- 03 Push scored leads from a data platform into Freshworks CRM and route them by lifecycle stage.
- 04 Two-way sync accounts and deals with an ERP so quotes and invoices reference the same customer records.
Common sync patterns
Customer context in Treasuredata
Accounts, contacts, deals, and activity from Freshworks CRM sync into Treasuredata, so metrics and dashboards group by real customers, segments, and stage instead of anonymous IDs.
Report on live CRM data
New records and status changes in Freshworks CRM appear in Treasuredata within seconds, so dashboards and cohorts track the current pipeline rather than last night's export.
Where Freshworks CRM accepts updates: segments and scores back on the record
Cohorts, scores, and computed metrics from Treasuredata sync onto fields in Freshworks CRM, putting the analysis where reps and owners actually work the accounts.
What you can sync between Freshworks CRM and Treasuredata
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.
| Freshworks CRM objects | Treasuredata objects | How this pairing syncs | |
|---|---|---|---|
| Notes Context records attached to contacts, accounts, and deals. | Query Jobs Ad-hoc Presto/Trino query jobs run asynchronously; results are retrieved from the job result endpoint and fed into downstream systems. | Notes is specific to Freshworks CRM and Query Jobs to Treasuredata — each maps to any object or custom field on the other side. | |
| Contacts Unified sales-and-marketing person records; the core entity for bidirectional syncs. | Databases Logical containers for tables; a sync targets one database and maps its tables to warehouse or operational-DB tables. | Contacts is specific to Freshworks CRM and Databases to Treasuredata — each maps to any object or custom field on the other side. | |
| Accounts Company records kept consistent with ERP and billing systems. | Tables Columnar log tables in TD's Plazma storage; every row carries a mandatory `time` column (Unix epoch) that Stacksync uses as the incremental watermark and partition key. Synced two-way with warehouse or database tables. | Accounts is specific to Freshworks CRM and Tables to Treasuredata — each maps to any object or custom field on the other side. | |
| Deals Pipeline records synced out for forecasting and full-funnel reporting. | Master (Parent) Segments Unified customer profiles assembled from multiple source tables in Audience Studio; read out to push enriched attributes onto CRM or warehouse records. | Deals is specific to Freshworks CRM and Master (Parent) Segments to Treasuredata — each maps to any object or custom field on the other side. | |
| Tasks Follow-ups created from external signals such as product usage events. | Segments Campaign subsets of a parent segment; membership read out to activate audiences in downstream systems, or audience flags written back onto records. | Tasks is specific to Freshworks CRM and Segments to Treasuredata — each maps to any object or custom field on the other side. | |
| Appointments Meeting records readable for activity reporting. | Journeys Timeline-based event sequences in Audience Studio; stage and membership read out for reporting and cross-system activation. | Appointments is specific to Freshworks CRM and Journeys to Treasuredata — each maps to any object or custom field on the other side. |
How changes propagate between Freshworks CRM and Treasuredata
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.
Freshworks CRM Treasuredata Sub-second propagation
DetectionFreshworks CRM notifies Stacksync of record changes through webhook events. Polling with updated-at filters.
DeliveryEach detected change is written to Treasuredata through its API, with automatic retries and rate-limit backoff.
Treasuredata Freshworks CRM Interval-based propagation
DetectionStacksync polls Treasuredata for changes on an incremental schedule, reading only records changed since the previous pass. Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column.
DeliveryEach detected change is written to Freshworks CRM through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Freshworks CRM: Subject to per-account API rate limits that vary by plan.
- Treasuredata: TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs.
What ships with Freshworks CRM ⇄ Treasuredata
Connect Freshworks CRM and Treasuredata for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Freshworks CRM–Treasuredata connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Freshworks CRM or Treasuredata 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 Freshworks CRM or Treasuredata record.
Observability
Monitoring
Track your Freshworks CRM ⇄ Treasuredata sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Freshworks CRM and Treasuredata.
How the Freshworks CRM and Treasuredata connectors work
Freshworks CRM
- Integration surface
- REST API
- Authentication
- API key sent as a Token authorization header
- Change detection
- Polling with updated-at filters; outbound webhooks can be configured through workflow automations
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to per-account API rate limits that vary by plan
Treasuredata
- Integration surface
- TD API v3 (REST) for databases, tables, and jobs, plus the Audience API (REST) for CDP segments and journeys
- Authentication
- API key sent as an `Authorization: TD1 <api_key>` header (per-user or account key from the TD Console); requests go to the region-specific endpoint (e.g. api.treasuredata.com for US, with separate EU and Tokyo endpoints)
- Change detection
- Polling on the mandatory `time` column (Unix-epoch partition key) or an updated-at column; TD stores append-oriented columnar data with no per-row CDC stream, so incremental syncs query for rows past a stored watermark
- Capabilities
- read · write
- Rate limits
- TD does not publish a fixed request-per-second cap; query throughput is bounded by the account's compute resource pool and large reads/exports run as asynchronous jobs
How it works
How to connect Freshworks CRM to Treasuredata — 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 Freshworks CRM and Treasuredata with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Freshworks CRM
connected
Treasuredata
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Freshworks CRM and Treasuredata 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 · Freshworks CRM ⇄ TreasuredataCustomers 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.
Freshworks CRM TreasuredataCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Freshworks CRM and Treasuredata integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Freshworks CRM and Treasuredata: authenticate both systems, choose the objects to sync (such as Freshworks CRM's Notes and Contacts), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Treasuredata side: Journeys, Predictive Segments, Scheduled Queries, Query Jobs, plus custom fields where Treasuredata exposes them. On the Freshworks CRM side: Lists, Notes, Contacts, Accounts. 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 Freshworks CRM and Treasuredata: Customer context in Treasuredata; Report on live CRM data; Where Freshworks CRM accepts updates: segments and scores back on the record. Accounts, contacts, deals, and activity from Freshworks CRM sync into Treasuredata, so metrics and dashboards group by real customers, segments, and stage instead of anonymous IDs.
-
Freshworks CRM: REST API. Authentication: API key sent as a Token authorization header. Treasuredata: TD API v3 (REST) for databases, tables, and jobs, plus the Audience API (REST) for CDP segments and journeys. Authentication: API key sent as an `Authorization: TD1 <api_key>` header (per-user or account key from the TD Console); requests go to the region-specific endpoint (e.g. api.treasuredata.com for US, with separate EU and Tokyo endpoints). Stacksync manages authentication, retries, and rate limits on both sides.
-
Treasuredata: TD storage (Plazma) is append/columnar-oriented — there is no native per-row change-data-capture stream, so incremental reads rely on polling a time or updated-at column. Freshworks CRM: Contacts and accounts expose lifecycle stages and custom fields through the API, so one record serves both sales and marketing workflows. Stacksync's field mapping accounts for these differences between Freshworks CRM and Treasuredata without custom code.
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 396 integrations available for Freshworks CRM and Treasuredata.
Popular · 7 of 396
-
Freshworks CRM ⇄ Adobeanalytics -
Freshworks CRM ⇄ Pendo -
Freshworks CRM ⇄ Splunk -
Freshworks CRM ⇄ Mixpanel -
Treasuredata ⇄ Dun And Bradstreet -
Treasuredata ⇄ Seismic -
Treasuredata ⇄ Xactly
No integrations match .
