Real-time
Two-way sync
Changes in Easypost or Folk CRM instantly reflect in both systems. No stale data, no manual imports.
E-commerce ⇄ CRM
Easypost to Folk CRM integration — real-time, two-way sync
Keep Easypost and Folk CRM 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 Easypost and Folk CRM
Keep the customers and orders that Folk CRM and Easypost 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. Easypost 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 Reminders, People, Companies, Groups in Folk CRM to Tracker, Batch, CarrierAccount, Webhook in Easypost 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 Mirror folk groups into a reporting database to track pipeline and outreach coverage.
- 02 Keep folk and a billing or customer success tool aligned on company records as deals close.
- 03 Create a Tracker for every outbound shipment and stream tracker.updated webhook events into Postgres or a warehouse so support and ops see live delivery status beside order records.
- 04 Verify and normalize customer Addresses through EasyPost before they are saved to the CRM or OMS to cut failed deliveries and carrier address-correction surcharges.
Common sync patterns
One customer identity across sales and store
A person who exists as a contact in Folk CRM and a buyer in Easypost is kept as a single, deduplicated record, so both teams work from the same customer instead of two partial copies.
Where Easypost records orders: purchase history on the account
Orders and their status from Easypost 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 Easypost 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.
What you can sync between Easypost and Folk CRM
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.
| Easypost objects | Folk CRM objects | How this pairing syncs | |
|---|---|---|---|
| Address Origin and destination locations; create, retrieve, and list, plus address verification (delivery and residential) to normalize and validate addresses before they are saved downstream. | Notes Free-text context attached to people and companies, readable for reporting. | Address is specific to Easypost and Notes to Folk CRM — each maps to any object or custom field on the other side. | |
| Parcel Package dimensions and weight (or a predefined_package); created standalone or inline on a Shipment and reused across shipments and batches. | Reminders Follow-up items that can be created from external triggers. | Parcel is specific to Easypost and Reminders to Folk CRM — each maps to any object or custom field on the other side. | |
| Rate Carrier service and price options EasyPost generates on a Shipment; read-only - you select a rate id and buy it, you do not create or edit rates directly. | People Contact records; the primary entity synced with outreach and enrichment tools. | Rate is specific to Easypost and People to Folk CRM — each maps to any object or custom field on the other side. | |
| Tracker Tracking for a shipment by tracking_code and carrier; create a Tracker to begin tracking, read status and tracking_details, and receive tracker.updated events via webhook as the parcel moves. | Companies Organization records linked to people and kept aligned with billing or CS systems. | Tracker is specific to Easypost and Companies to Folk CRM — each maps to any object or custom field on the other side. | |
| Batch Bulk shipment processing; create a batch, add or remove shipments, buy all labels at once, and generate a consolidated label or ScanForm for the day's orders. | Groups Shared workspaces that organize contacts; group membership is often the field integrations act on. | Batch is specific to Easypost and Groups to Folk CRM — each maps to any object or custom field on the other side. | |
| CarrierAccount Carrier credentials and settings that control which carriers and negotiated rates are available; create, update, and delete to manage enabled carriers across accounts. | Custom fields Group-scoped attributes that receive enriched or computed values from external systems. | CarrierAccount is specific to Easypost and Custom fields to Folk CRM — each maps to any object or custom field on the other side. |
How changes propagate between Easypost and Folk CRM
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.
Easypost Folk CRM Sub-second propagation
DetectionEasypost notifies Stacksync of record changes through webhook events. Webhooks deliver an Event via HTTP POST on object changes (e.g.
DeliveryEach detected change is written to Folk CRM through its API, with automatic retries and rate-limit backoff.
Folk CRM Easypost 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 Easypost through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Easypost: Fixed 5 requests/second on index (list) endpoints plus a dynamic load-based limiter protecting buy and rate operations; exceeding either returns HTTP 429 Too Many Requests.
- Folk CRM: Subject to the platform's API rate limits.
What ships with Easypost ⇄ Folk CRM
Connect Easypost and Folk CRM for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Easypost–Folk CRM connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Easypost or Folk CRM 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 Easypost or Folk CRM record.
Observability
Monitoring
Track your Easypost ⇄ Folk CRM sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Easypost and Folk CRM.
How the Easypost and Folk CRM connectors work
Easypost
- Integration surface
- REST API (EasyPost API v2, https://api.easypost.com/v2)
- Authentication
- HTTP Basic auth with the API key as the username and an empty password (Bearer token also accepted); separate Test and Production keys
- Change detection
- Webhooks deliver an Event via HTTP POST on object changes (e.g. tracker.updated); historical pulls via list/index endpoints using before_id/after_id cursor pagination
- Capabilities
- read · write · webhooks
- Rate limits
- Fixed 5 requests/second on index (list) endpoints plus a dynamic load-based limiter protecting buy and rate operations; exceeding either returns HTTP 429 Too Many Requests
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
How it works
How to connect Easypost to Folk CRM — 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 Easypost and Folk CRM with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Easypost
connected
Folk CRM
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Easypost and Folk CRM 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 · Easypost ⇄ Folk CRMCustomers 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.
Easypost Folk CRMCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Easypost and Folk CRM integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Easypost and Folk CRM: authenticate both systems, choose the objects to sync (such as Easypost's Address and Parcel), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Common patterns for Easypost and Folk CRM: One customer identity across sales and store; Where Easypost records orders: purchase history on the account; New buyers become CRM records. A person who exists as a contact in Folk CRM and a buyer in Easypost is kept as a single, deduplicated record, so both teams work from the same customer instead of two partial copies.
-
Easypost: REST API (EasyPost API v2, https://api.easypost.com/v2). Authentication: HTTP Basic auth with the API key as the username and an empty password (Bearer token also accepted); separate Test and Production keys. Folk CRM: REST API. Authentication: API key (Bearer token). Stacksync manages authentication, retries, and rate limits on both sides.
-
Folk CRM: The API surface covers people, companies, groups, deals, notes, reminders, and interactions, plus webhook subscriptions for record events. Easypost: Rates are generated by EasyPost, not written - you create a Shipment, receive a set of Rate options, then buy against the chosen rate id, and the label (postage_label) and tracking_code come back on the purchased Shipment. Stacksync's field mapping accounts for these differences between Easypost and Folk CRM 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 Easypost and Folk CRM records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Easypost and Folk CRM connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Easypost–Folk CRM integration in-house.
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 Easypost and Folk CRM.
Popular · 5 of 374
-
Easypost ⇄ SAP Sales Cloud -
Easypost ⇄ Streak CRM -
Easypost ⇄ SugarCRM -
Folk CRM ⇄ Bigcommerce -
Folk CRM ⇄ Magento
No integrations match .
