---
title: "Intercom Connector | Tajo"
description: "Tajo does not run a Intercom connector today. Early code exists; this page lists what it does and what is planned."
url: https://tajo.io/docs/connectors/support/intercom/
markdown: https://tajo.io/docs/connectors/support/intercom.md
lang: en-US
author: "Set Noa"
author_url: https://tajo.io/set-noa/
robots: noindex
---

# Intercom Connector

[Set Noa](https://tajo.io/set-noa/)

Connector status: Planned Not built yet. Tajo does not run this connector today.

| Source field | Destination field | Sample value |
| --- | --- | --- |
| `record.id` | `source_id` | `record_1042` |
| `record.updated_at` | `updated_at` | `2026-10-18T08:00:00Z` |
| `record.value` | `value` | `sample_value` |

Tajo does not run a Intercom connector today. Early code exists, but it has not been run against a live Intercom account and syncs nothing yet.

## What exists so far

- Reads contacts, companies and the workspace’s admins.

## Planned, not built

- Two-way contact sync
- Conversation data
- Custom events and tags

## Open-Source Implementation Map

This section is derived from official or public repository material discovered for the Intercom connector. Use it as the engineering companion to the setup guide above: it shows where the API surface lives, what implementation assets exist, and how Tajo should translate them into reliable Brevo sync behavior.

### Repository Snapshot

| Repository | Commit | Languages / formats | Files |
| --- | --- | --- | --- |
| [intercom/Intercom-OpenAPI](https://github.com/intercom/Intercom-OpenAPI) | 58585fd | JSON (24), Markdown (22), JavaScript (17), YAML (12), YAML (10), sh (1) | 90 |
| [intercom/intercom-mcp-server](https://github.com/intercom/intercom-mcp-server) | 96140be | svg (4), Markdown (1) | 5 |

### Integration Shape

```mermaid
graph LR
  Source["Intercom API / repository"] --> Auth["Auth and scopes"]
  Source --> Objects["Objects, events, and schemas"]
  Auth --> Tajo["Tajo connector runtime"]
  Objects --> Tajo
  Tajo --> Brevo["Brevo contacts, attributes, lists, campaigns"]
  Tajo --> Ops["Backfill, cursor, retries, logs"]
```

### What To Reuse

- Intercom REST API OpenAPI Description
- This repository contains OpenAPI descriptions for Intercom’s REST API.
- It defines the HTTP interface used to integrate with Intercom’s customer engagement and support platform.
- **Supported API versions:** 2.7 and higher.

---

### Tajo Revamp Checklist

- Keep authentication setup aligned with the vendor docs and the public repository’s current API shape.
- Map primary resources into explicit Tajo sync objects with stable external IDs.
- Prefer cursor-based or updated-at incremental sync where the API exposes it; otherwise document the fallback.
- Treat webhook handlers as idempotent and replay-safe, especially for order, contact, ticket, and campaign events.
- Capture pagination, rate limits, retry headers, and partial-failure behavior in connector smoke tests.
- Keep examples small and runnable against sandbox or test-mode accounts.

### Sources

- [intercom/Intercom-OpenAPI](https://github.com/intercom/Intercom-OpenAPI)
- [intercom/intercom-mcp-server](https://github.com/intercom/intercom-mcp-server)
- [Vendor documentation](https://developers.intercom.com/)