> For the complete documentation index, see [llms.txt](https://docs.graphlit.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.graphlit.dev/api-guides/use-cases/feeds/messaging/feed-create-intercom-articles.md).

# Create Intercom Articles Feed

## User Intent

"How do I sync Intercom Help Center articles? Show me Intercom Articles feed configuration."

## Operation

**SDK Method**: `createFeed()` with FeedTypes.Intercom\
**Auth**: Intercom access token

***

## Code Example (TypeScript)

```typescript
import { Graphlit } from 'graphlit-client';
import { FeedTypes, FeedServiceTypes } from 'graphlit-client/dist/generated/graphql-types';

const graphlit = new Graphlit();

const feed = await graphlit.createFeed({
  name: 'Help Center',
  type: FeedTypes.Intercom,
  intercom: {
    type: FeedServiceTypes.IntercomArticles,
    accessToken: process.env.INTERCOM_TOKEN!,
    readLimit: 200,
  },
  // Optional: add workflow for content processing
  // workflow: { id: workflow.createWorkflow.id }
});

console.log(`Created Intercom Articles feed: ${feed.createFeed.id}`);
```

***

## Configuration

**type**: `FeedServiceTypes.IntercomArticles`\
**accessToken**: Intercom access token\
**readLimit**: Number of articles to sync

***

## Intercom Token Setup

1. Go to Intercom → Settings → Developers → Developer Hub
2. Create new app or select existing app
3. Configure OAuth scopes: `Read articles`
4. Generate access token
5. Set `INTERCOM_TOKEN` environment variable

***

## What Gets Synced

* Help Center article titles and content
* Article collections and sections
* Article metadata (author, status, dates)
* Article URLs and translations
* Article statistics (views, reactions)

***

## IntercomArticles vs IntercomTickets

**Use IntercomArticles for:**

* Help Center content
* Knowledge base articles
* Self-service documentation
* Product guides
* FAQ content

**Use IntercomTickets for:**

* Customer support conversations
* Support tickets
* User inquiries
* Chat transcripts

***

## Use Cases

**Product Documentation**:

```typescript
type: FeedServiceTypes.IntercomArticles
```

**Customer Self-Service**:

```typescript
type: FeedServiceTypes.IntercomArticles,
readLimit: 500  // Large knowledge base
```

**Multi-language Support**:

```typescript
// Intercom automatically includes article translations
type: FeedServiceTypes.IntercomArticles
```

***

## Intercom API Scopes

Required OAuth scopes:

* `Read articles` - Access help center articles
* `Read collections` - Access article collections

Optional scopes:

* `Read admins` - Get article author info
* `Read teams` - Get team assignments

***

## Related

* [Intercom Tickets Feed](/api-guides/use-cases/feeds/messaging/feed-create-intercom.md) - Support conversations
* [Zendesk Articles](/api-guides/use-cases/feeds/project-management/feed-create-zendesk-articles.md) - Zendesk knowledge base
* [Notion Feed](/api-guides/use-cases/feeds/project-management/feed-create-notion.md) - Notion docs


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.graphlit.dev/api-guides/use-cases/feeds/messaging/feed-create-intercom-articles.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.