Skip to content

Keep Intercom in Sync With WordPress (Without CSV Exports)

Contacts, roles, and purchase activity stay current. Not whenever someone remembers to export a CSV.

Keeping Intercom in sync with WordPress means contacts and roles update as they change on the site. For stores, purchase activity comes along too. You are not waiting on a Friday CSV. Sync Engine for Intercom runs on your WordPress site and pushes changes to Intercom in the background, with queued jobs and retries.

Sync users and roles, WordPress events, WooCommerce events, custom mapping, bulk backfill, advanced metrics, and tag automation from one plugin.

WordPress Intercom integration

The real cost of “we’ll sync it later”

  • Stale plans and roles drive the wrong automations
  • Support copies data by hand mid-ticket
  • Zapier task surprises show up after a sale spike
  • Someone stays on-call for custom scripts that break after an update

Stale Intercom is not a soft problem. It is wrong messages, longer tickets, and silent automation failures.

Three brittle approaches

CSV imports

Slow, error-prone, and always looking backward. Fine once. A bad habit every Friday.

Zapier / Make patchwork

Flexible glue. Expensive or fragile when store volume climbs. Full comparison: Zapier vs Sync Engine.

Custom Intercom builds

A custom integration means you write and maintain the connection. You also own every break when Intercom or WordPress ships a change. Sync Engine is the plugin path.

What “in sync” should include

  • Users and identity (email, profile fields, a stable link between WordPress and Intercom)
  • Roles as tags, with tag automation when roles change
  • Woo customers, orders, and events (WooCommerce sync)
  • Attributes and KPIs
  • Optional Messenger identity verification

How Sync Engine keeps sync trustworthy

  • Queued jobs with retries, running in the background on your WordPress site
  • Bulk sync in small batches you can stop, with progress
  • Each order is sent once, in background batches on your WordPress site
  • OAuth or Access Token; Connected / Not Connected status and a test connection
  • When a WordPress user is deleted, the plugin clears its local link to that Intercom contact. The Intercom contact stays in Intercom. Turn on User Deleted under Events if you want that event sent.

Switch off CSV exports and overlapping Zaps

Step 1
Install and connect

Install the plugin. Connect with OAuth or an Access Token.

Step 2
Prove a small sync

Sync a small test role first. Know which fields matter before you touch production automations.

Step 3
Enable the depth you need

Turn on Woo events, custom mapping, or bulk backfill as your stack requires.

Step 4
Turn off overlapping writers

Turn off overlapping Zaps and the CSV habit so you are not writing the same contact twice.

Step 5
Validate Intercom automations

Confirm segments and messages still fire on the attributes you expect.

Step 6
Keep incremental sync on

Leave incremental sync on, and keep the old writers off.

Bulk details: Bulk sync WordPress users to Intercom.

Plan details live on the WordPress Intercom plans page.

FAQ

Can I keep Intercom in sync without CSV?
Yes. Sync Engine for Intercom pushes changes from WordPress.
Do I need Zapier?
No. Sync Engine connects WordPress to Intercom directly.
Does this include Woo events?
Yes. Enable WooCommerce events under Events. See WooCommerce sync.
Is Messenger required?
No.
Where does data go?
Credentials stay on your WordPress site. Sync goes WordPress → Intercom.
Where can I see pricing?
See pricing on the product page.

Stop exporting CSVs to keep Intercom current

Install free, connect with OAuth or an Access Token, then turn on the sync depth your stack needs.

Install free on WordPress.org

See WordPress Intercom integration