Real-time
Two-way sync
Changes in Folk CRM or Shipwire instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ E-commerce
Folk CRM to Shipwire integration — real-time, two-way sync
Keep Folk CRM and Shipwire 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 Shipwire
Keep the customers and orders that Folk CRM and Shipwire share aligned in real time, so sales works from live purchase history and the store works from current account details.
Folk CRM holds the customer relationship: the contacts, accounts, and deals a go-to-market team works. Shipwire runs the buying side: who placed which order, what they bought, and where it ships. The two describe the same people and companies, and when they are connected only by exports, sales answers questions without recent orders in front of them while the store works from account details that changed weeks ago.
Stacksync links People, Companies, Groups, Custom fields in Folk CRM to Rates, Orders, Products, Stock in Shipwire with bi-directional, real-time sync. New customers, order activity, and corrected contact details move in whichever direction you configure, field by field, with conflicts resolved by rules you set. A record created or changed on either side shows up on the other within seconds, with no CSV exports and no nightly job.
The shared entity is the customer, matched on email or an external ID, so both systems agree on who the buyer is and the order history sits next to the relationship instead of in a separate tab.
Common use cases
- 01 Sync folk people and companies with a marketing or outbound tool so outreach lists stay current.
- 02 Push enriched contact data from a data warehouse into folk custom fields.
- 03 Pull Returns and tracking.delivered events into a support or analytics database for reverse-logistics and delivery-SLA reporting.
- 04 Two-way sync Orders between a storefront or ERP database and Shipwire so new orders create fulfillment requests and Stacksync writes Trackings and status (processed, submitted, delivered) back.
Common sync patterns
Where Shipwire records orders: purchase history on the account
Orders and their status from Shipwire appear on the matching contact or account in Folk CRM, so reps see what a customer has bought and what is in flight before the next conversation.
New buyers become CRM records
A customer created in Shipwire creates or updates the matching contact or account in Folk CRM, so first-time and repeat buyers land in the relationship system without a manual import.
Contact and address details stay consistent
An email, phone, or shipping and billing address corrected in either system updates the other, so the next order and the next outreach both use current information.
What you can sync between Folk CRM and Shipwire
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 | Shipwire objects | How this pairing syncs | |
|---|---|---|---|
| Custom fields Group-scoped attributes that receive enriched or computed values from external systems. | Stock Real-time per-warehouse inventory levels; read-only, pulled into a database or storefront so availability reflects on-hand and backordered quantities. | Custom fields is specific to Folk CRM and Stock to Shipwire — each maps to any object or custom field on the other side. | |
| Notes Free-text context attached to people and companies, readable for reporting. | Receivings Inbound advance ship notices (ASNs) from suppliers; created and updated via API and reconciled against Purchase Orders as inventory arrives at a warehouse. | Notes is specific to Folk CRM and Receivings to Shipwire — each maps to any object or custom field on the other side. | |
| Reminders Follow-up items that can be created from external triggers. | Returns Return orders raised against existing Orders; created via API and read back into support or analytics systems for reverse-logistics tracking. | Reminders is specific to Folk CRM and Returns to Shipwire — each maps to any object or custom field on the other side. | |
| People Contact records; the primary entity synced with outreach and enrichment tools. | Purchase Orders B2B orders with retailer-specific routing and compliance fields; managed via API alongside receivings for wholesale and marketplace fulfillment. | People is specific to Folk CRM and Purchase Orders to Shipwire — 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. | Trackings Shipment tracking numbers and carrier status returned as an Order subresource and surfaced through tracking.created, tracking.updated, and tracking.delivered webhook topics. | Companies is specific to Folk CRM and Trackings to Shipwire — 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. | Rates Shipping cost quotes for a cart or order; read-only, called at checkout time to estimate carrier costs rather than synced as stored records. | Groups is specific to Folk CRM and Rates to Shipwire — each maps to any object or custom field on the other side. |
How changes propagate between Folk CRM and Shipwire
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 Shipwire 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 Shipwire through its API, with automatic retries and rate-limit backoff.
Shipwire Folk CRM Sub-second propagation
DetectionShipwire notifies Stacksync of record changes through webhook events. Webhooks (HMAC-SHA256 signed, near real-time) on order, tracking, stock, receiving, return, and product topics.
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.
- Shipwire: No published per-second request cap; list responses page at 20 items (recommended max ~200) and webhook payloads carry at most 20 items per resource, so large records must be paged via the response next links.
What ships with Folk CRM ⇄ Shipwire
Connect Folk CRM and Shipwire for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Folk CRM–Shipwire connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Folk CRM or Shipwire 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 Shipwire record.
Observability
Monitoring
Track your Folk CRM ⇄ Shipwire 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 Shipwire.
How the Folk CRM and Shipwire 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
Shipwire
- Integration surface
- REST API (v3)
- Authentication
- Bearer token sent as `Authorization: ShipwireKey <token>`; up to two keys are generated per account on the Users and Roles page, refreshable/expirable, over HTTPS only (separate sandbox at api.beta.shipwire.com)
- Change detection
- Webhooks (HMAC-SHA256 signed, near real-time) on order, tracking, stock, receiving, return, and product topics; polling the list endpoints as a fallback (no CDC/log stream)
- Capabilities
- read · write · webhooks
- Rate limits
- No published per-second request cap; list responses page at 20 items (recommended max ~200) and webhook payloads carry at most 20 items per resource, so large records must be paged via the response next links.
How it works
How to connect Folk CRM to Shipwire — 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 Shipwire 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
Shipwire
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Folk CRM and Shipwire 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 ⇄ ShipwireCustomers 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 ShipwireCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Folk CRM and Shipwire integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Folk CRM and Shipwire: authenticate both systems, choose the objects to sync (such as Folk CRM's Custom fields and Notes), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Folk CRM and Shipwire. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Folk CRM: Webhook subscriptions for record events, with polling of list endpoints as a fallback. On Shipwire: Webhooks (HMAC-SHA256 signed, near real-time) on order, tracking, stock, receiving, return, and product topics; polling the list endpoints as a fallback (no CDC/log stream). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Folk CRM side: People, Companies, Groups, Custom fields, plus custom fields where Folk CRM exposes them. On the Shipwire side: Rates, Orders, Products, Stock. 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 Shipwire: Where Shipwire records orders: purchase history on the account; New buyers become CRM records; Contact and address details stay consistent. Orders and their status from Shipwire appear on the matching contact or account in Folk CRM, so reps see what a customer has bought and what is in flight before the next conversation.
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 374 integrations available for Folk CRM and Shipwire.
Popular · 7 of 374
-
Folk CRM ⇄ Shopware -
Folk CRM ⇄ Akeneo -
Folk CRM ⇄ Bigcommerce -
Shipwire ⇄ Gladly -
Shipwire ⇄ Gorgias -
Shipwire ⇄ Infor CRM -
Shipwire ⇄ Insightly
No integrations match .
