Real-time
Two-way sync
Changes in Folk CRM or Servicemax instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ Business productivity
Folk CRM to Servicemax integration — real-time, two-way sync
Keep Folk CRM and Servicemax 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 Folk CRM and Servicemax
Sync what happens in Servicemax with the customer records in Folk CRM, in real time and in both directions.
The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Servicemax holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.
Stacksync connects Products, Work Orders, Work Details, Installed Products in Servicemax to Groups, Custom fields, Notes, Reminders in Folk CRM with bi-directional, real-time sync. Activity and record changes in Servicemax update the matching contact or account in Folk CRM, and CRM data flows the other way wherever Servicemax can store and use it.
Common use cases
- 01 Consolidate Service Contracts and entitlement data into a warehouse for renewal forecasting and SLA compliance dashboards.
- 02 Mirror Accounts and Contacts between ServiceMax and the CRM system of record so customer and site data stays consistent.
- 03 Push enriched contact data from a data warehouse into folk custom fields.
- 04 Mirror folk groups into a reporting database to track pipeline and outreach coverage.
Common sync patterns
Where Servicemax processes payments
Charges, refunds, and subscription changes appear on the account in Folk CRM, so revenue context lives with the relationship.
Where Servicemax can store CRM context: fields kept current
Owner, lifecycle stage, or account details from Folk CRM sync into Servicemax, so people working there have the context without switching tools.
Where Servicemax supplies contact or company data
Enriched fields land directly on records in Folk CRM, and refreshes keep them from going stale.
What you can sync between Folk CRM and Servicemax
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.
| Folk CRM objects | Servicemax objects | How this pairing syncs | |
|---|---|---|---|
| Reminders Follow-up items that can be created from external triggers. | Products Standard Salesforce Product2; catalog of serviceable products and spare parts referenced by Installed Products and Work Details. | Reminders is specific to Folk CRM and Products to Servicemax — each maps to any object or custom field on the other side. | |
| People Contact records; the primary entity synced with outreach and enrichment tools. | Work Orders SVMXC__Service_Order__c; the core field-service job record for install, repair, and maintenance; synced two-way with databases and pushed to ERPs at close. | People is specific to Folk CRM and Work Orders to Servicemax — each maps to any object or custom field on the other side. | |
| Companies Organization records linked to people and kept aligned with billing or CS systems. | Work Details SVMXC__Service_Order_Line__c; line items on a Work Order for labor, parts used, and expenses; read out for billing or written back with usage. | Companies is specific to Folk CRM and Work Details to Servicemax — each maps to any object or custom field on the other side. | |
| Groups Shared workspaces that organize contacts; group membership is often the field integrations act on. | Installed Products SVMXC__Installed_Product__c; the installed-base asset record driving entitlement and service history; synced with asset and IoT databases. | Groups is specific to Folk CRM and Installed Products to Servicemax — each maps to any object or custom field on the other side. | |
| Custom fields Group-scoped attributes that receive enriched or computed values from external systems. | Service Contracts SVMXC__Service_Contract__c; coverage and entitlement agreements; synced to warehouses for renewal, SLA, and warranty reporting. | Custom fields is specific to Folk CRM and Service Contracts to Servicemax — each maps to any object or custom field on the other side. | |
| Notes Free-text context attached to people and companies, readable for reporting. | Stock History SVMXC__Stock_History__c; append-only log of inventory transactions (RMA, shipment, parts receipt); read out for parts and inventory analytics. | Notes is specific to Folk CRM and Stock History to Servicemax — each maps to any object or custom field on the other side. |
How changes propagate between Folk CRM and Servicemax
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.
Folk CRM Servicemax Sub-second propagation
DetectionFolk CRM notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling of list endpoints as a fallback.
DeliveryEach detected change is written to Servicemax through its API, with automatic retries and rate-limit backoff.
Servicemax Folk CRM Sub-second propagation
DetectionChanges in Servicemax are captured at the source via change data capture — no polling loop against its API. Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object.
DeliveryEach detected change is written to Folk CRM through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Folk CRM: Subject to the platform's API rate limits.
- Servicemax: Governed by the Salesforce org-wide daily API request allocation, shared across all integrations and scaled by edition and license count.
What ships with Folk CRM ⇄ Servicemax
Connect Folk CRM and Servicemax for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Folk CRM–Servicemax connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Folk CRM or Servicemax 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 Folk CRM or Servicemax record.
Observability
Monitoring
Track your Folk CRM ⇄ Servicemax sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Folk CRM and Servicemax.
How the Folk CRM and Servicemax connectors work
Folk CRM
- Integration surface
- REST API
- Authentication
- API key (Bearer token)
- Change detection
- Webhook subscriptions for record events, with polling of list endpoints as a fallback
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
Servicemax
- Integration surface
- Salesforce REST, SOAP, and Bulk APIs (ServiceMax is a managed package on the Salesforce platform)
- Authentication
- Salesforce OAuth login via a user with API access; the connecting profile needs object and field permissions on ServiceMax's SVMXC__ objects
- Change detection
- Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object where enabled
- Capabilities
- read · write · CDC
- Rate limits
- Governed by the Salesforce org-wide daily API request allocation, shared across all integrations and scaled by edition and license count
How it works
How to connect Folk CRM to Servicemax — 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 Folk CRM and Servicemax with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Folk CRM
connected
Servicemax
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Folk CRM and Servicemax 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 · Folk CRM ⇄ ServicemaxCustomers 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.
Folk CRM ServicemaxCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Folk CRM and Servicemax integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Folk CRM and Servicemax: authenticate both systems, choose the objects to sync (such as Folk CRM's Reminders and People), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Change detection on Folk CRM: Webhook subscriptions for record events, with polling of list endpoints as a fallback. On Servicemax: Salesforce mechanisms — Apex triggers or polling on SystemModstamp/LastModifiedDate, with Change Data Capture / Platform Events available per object where enabled. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Servicemax side: Products, Work Orders, Work Details, Installed Products, plus custom fields where Servicemax exposes them. On the Folk CRM side: Groups, Custom fields, Notes, Reminders. 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 Folk CRM and Servicemax: Where Servicemax processes payments; Where Servicemax can store CRM context: fields kept current; Where Servicemax supplies contact or company data. Charges, refunds, and subscription changes appear on the account in Folk CRM, so revenue context lives with the relationship.
-
Folk CRM: REST API. Authentication: API key (Bearer token). Servicemax: Salesforce REST, SOAP, and Bulk APIs (ServiceMax is a managed package on the Salesforce platform). Authentication: Salesforce OAuth login via a user with API access; the connecting profile needs object and field permissions on ServiceMax's SVMXC__ objects. Stacksync manages authentication, retries, and rate limits on both sides.
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 421 integrations available for Folk CRM and Servicemax.
Popular · 6 of 421
-
Folk CRM ⇄ SendGrid -
Folk CRM ⇄ Twilio -
Servicemax ⇄ Gladly -
Servicemax ⇄ Gorgias -
Servicemax ⇄ Infor CRM -
Servicemax ⇄ Insightly
No integrations match .
