Docs
← Back to site

Importing from Intercom

2 min readUpdated October 29, 2026

Unlike the weDocs importer, this one connects live to the Intercom API, so it works even if Intercom isn’t installed anywhere near this WordPress site. It always imports your entire Help Center in one go, there’s no way to pick just one section.

Getting an access token#

In your Intercom dashboard, go to Settings → Developer Hub → New app, and set its permissions to at least Read on Articles. Copy the resulting access token.

The token is used only for this one import request and is never saved to your database, you’ll need to paste it in again if you want to re-import later.

Running the import#

Go to WP Super Docs → Import, choose Intercom as the source, and fill in:

  • Access token: the token from Intercom’s Developer Hub.
  • Assign to product: which existing WP Super Docs product every imported article goes under.
  • Include drafts: checked to also import articles that aren’t published in Intercom yet.
  • Duplicate handling: skip anything whose slug already exists, or update existing docs whose slug matches.
The Intercom importer with the access token and product fields.

Click Import from Intercom. There’s no separate “test connection” step, if the token is invalid or lacks permission, you’ll find out from an error message after clicking import, rather than beforehand.

How the structure maps over#

  • Collections become categories.
  • Articles become docs, with their HTML body carried over directly (Intercom already stores article bodies as HTML, so this comes across cleanly).

Intercom lets you organize articles into Sections nested inside a Collection, not just directly inside a Collection. Only articles filed directly under a Collection get their category assigned correctly; an article filed inside a Section within a Collection imports successfully but without a category, since the importer only recognizes a direct Collection as a parent. If you use Sections in Intercom, plan to manually assign categories to those articles after importing.

Scale#

Intercom’s API is fetched in pages of 150 items, up to 50 pages per fetch (collections and articles are fetched separately), so up to 7,500 of each. This comfortably covers the vast majority of Help Centers; only exceed it on genuinely enormous documentation sites.

What isn’t preserved#

  • Slugs are generated from the title, since Intercom’s API doesn’t expose a slug field. Two articles with very similar titles could end up with WordPress auto-appending -2 to keep slugs unique.
  • Matching for updates is by slug only, the same limitation as the weDocs importer: if a title changes between imports, it won’t be recognized as the same article and will be created again instead of updated.

Was this helpful?

This website uses cookies to enhance your browsing experience and ensure the site functions properly. By continuing to use this site, you acknowledge and accept our use of cookies.

Accept All Accept Required Only