Ship deep Intercom integrations in days

Intercom holds conversations, contacts, tickets, and help center content behind separate APIs, and every workspace adds its own data attributes. With Ampersand, you can get this integration live for your customers in days.

Schedule a demo See Intercom guide

Build a custom data model to handle complex configurations

No two Intercom workspaces are the same. Every customer has custom data attributes, ticket types, and their own teams and tags. AI agents need infrastructure that understands Intercom at the per-tenant level.

3 / 4 customers

3 / 8 customers
  • Customer A: Conversation (standard), Contact (standard), Plan Tier (custom)
  • Customer B: Ticket (standard), Company (standard), Tag (standard)
  • Customer C: Contact (standard), Article (standard), Account Health (custom)

Enable software and agents to take bi-directional action

With Ampersand, your engineers don’t need to learn Intercom’s conversation, contact, and help center APIs. Simply declare the actions you want your agents to take: read, write, proxy.

Example. Read: “Sync every conversation that changed since the last run.”

  1. Ampersand uses this customer’s Intercom OAuth token.
  2. Ampersand searches for only the conversations updated since the last sync.
  3. The changed conversations come back, page by page.
  4. Ampersand applies this customer’s field mappings.
  5. Ampersand sends the conversations to your product.

Ensure your Intercom integration is always available

  • Managed auth

    Fully offload Intercom OAuth. Ampersand stores and refreshes tokens for every customer’s workspace.

  • Incremental reads

    After a full historic backfill, conversation, contact, and ticket syncs read only the records that changed.

  • Schema drift detection

    Get notified when fields are created, deleted, or changed in any customer’s Intercom, before the change breaks your integration.

Not all Intercom integrations are created equal

Intercom is where many teams talk to their customers, from support conversations to help center articles. With Ampersand, your developers can create a best-in-class Intercom integration.

In-House DIY Build Unified APIs Embedded iPaaS Ampersand
Data schema that works for all customers Lots of switch statements and special casesOnly access standard objects and fieldsBuild customer-specific workflows Flexible model with mappings
Object coverage Write and maintain clients for conversations, contacts, and ticketsOnly common models and their standard fieldsLimited to the objects its prebuilt actions cover Conversations, contacts, tickets, help center content, and more
Schema drift protection Manual incident debuggingNot supportedNot supported Get notified about schema changes
OAuth token custody You own the tokens, but you also have to manage refreshesVendor lock-inVendor lock-in Export at any time via API
Integration workflow Imperative custom codeSingle API clientDrag-and-drop, not integrated with Git Declarative manifest you can version control
Build vs. Buy Unified API vs. Ampersand

The Intercom objects your agents can read and write

Ampersand reads and writes Intercom conversations, contacts, tickets, and help center content, and reads workspace data such as admins, teams, and segments.

Objects What’s included Read Write
Conversations and tickets
  • Conversations
  • Tickets
  • Ticket types
Supported Supported
Contacts and companies
  • Contacts
  • Companies
  • Data attributes
  • Events
  • Tags
Supported Supported
Help center and news
  • Articles
  • Collections
  • News items
Supported Supported
Workspace
  • Admins
  • Teams
  • Segments
  • Help centers
  • Newsfeeds
  • Subscription types
  • Activity logs
Supported Not supported

Incremental reads cover conversations, contacts, tickets, and activity logs; other objects are read in full on each scheduled read.

See every object in the docs

Questions people ask before they book a demo

  • Which Intercom objects can I read and write?

    You can read and write conversations, tickets, contacts, companies, data attributes, events, tags, articles, collections, and news items. Admins, teams, segments, and activity logs are read-only.

  • Does Ampersand read only the records that changed?

    For conversations, contacts, tickets, and activity logs, yes: after a full historic backfill, Read Actions pick up only changed records. Other objects are read in full on each scheduled read.

  • How do my customers connect Intercom?

    You create an Intercom app with OAuth turned on and add its client ID and secret to Ampersand. Your customers then sign in with OAuth, and Ampersand stores and refreshes their tokens.

  • Does Ampersand offer a unified API?

    Ampersand doesn’t offer a unified API. It works with Intercom’s own objects and fields as each customer sets them up, which differs from how a unified API works. We also give you the primitives to build your own unified data model.