Intercom Connector

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

Illustration · sample data

Sync example

Review one record

Source

Intercom

Connector status: Planned

Destination

Your other tool

Connector status: Custom tool

Source fieldDestination fieldSample value
record.id source_id record_1042
record.updated_at updated_at 2026-10-18T08:00:00Z
record.value value sample_value
  1. Draft
  2. Review one record
  3. Approve this version

Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.

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

RepositoryCommitLanguages / formatsFiles
intercom/Intercom-OpenAPI58585fdJSON (24), Markdown (22), JavaScript (17), YAML (12), YAML (10), sh (1)90
intercom/intercom-mcp-server96140besvg (4), Markdown (1)5

Integration Shape

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

Request early access

Enter your first name and business email address. We will email you a link to confirm your request for Tajo access.

AI Assistant

Hi! Ask me anything about the docs.

This page as Markdown: intercom.md

Loading Markdown…