What makes Intercom notable?

1.1K downloads. Trust evidence available

How should Intercom be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Intercom

Intercom (intercom.com). Use this skill for ANY Intercom request — reading, creating, updating, and deleting data. Whenever a task involves Intercom, use this skill instead of calling the API directly.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.1k

Updated

Oct 11, 2026

Version

1.0.6

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.1K downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.6release · observed Sep 23, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-intercom

Install using `clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-intercom` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/oomol/oo-intercom before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-intercom/snapshot"

Documentation

CLAWHUB

53,269 characters of source documentation, loaded on request.

Extracted files

3 files captured from the source.

SKILL.md

---
name: oo-intercom
description: "Intercom (intercom.com). Use this skill for ANY Intercom request — reading, creating, updating, and deleting data. Whenever a task involves Intercom, use this skill instead of calling the API directly."
allowed-tools: [Bash(oo *)]
metadata:
  title: "Intercom"
  author: "OOMOL"
  version: "1.0.6"
  services: ["intercom"]
  icon: "https://static.oomol.com/logo/third-party/intercom.svg"
---

# Intercom

Operate **Intercom** through your OOMOL-connected account. This skill calls the `intercom` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.

## Running an action

Assume the user has already installed the oo CLI, signed in, and connected Intercom. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.

**1. Inspect the contract** to get the authoritative input/output schema before building a payload:

```bash
oo connector schema "intercom" --action "<action_name>"
```

**2. Run the action** with a JSON payload that matches the input schema:

```bash
oo connector run "intercom" --action "<action_name>" --data '<json>' --json
```

- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.
- The response is `{ "data": ..., "meta": { "executionId": "..." } }`; the execution id lives under `meta.executionId`.

Each action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.

## Available actions

- `close_conversation` — Close an Intercom conversation. [destructive]
- `create_contact` — Create a new Intercom contact. [write]
- `get_admin` — Get a single Intercom admin by identifier.
- `get_article` — Get a single Intercom help center article by identifier.
- `get_company` — Get a single Intercom company by company ID or name.
- `get_contact` — Get a single Intercom contact by identifier.
- `get_contact_by_external_id` — Get a single Intercom contact by external ID.
- `get_conversation` — Get a single Intercom conversation with its conversation parts.
- `get_counts` — Read Intercom workspace, conversation, or grouped counts.
- `get_current_admin` — Get the currently authorized Intercom admin and workspace metadata.
- `get_job_status` — Get the status of an Intercom asynchronous job.
- `get_ticket` — Get a single Intercom ticket by internal ticket identifier.
- `list_admins` — List Intercom admins for the current workspace.
- `list_articles` — List Intercom help center articles.
- `list_companies` — List Intercom companies with pagination.
- `list_contacts` — List Intercom contacts with cursor-based pagination.
- `list_conversations` — List Intercom conversations with cu

_meta.json

{
  "ownerId": "kn7fzg3sx4xr7ssnc2yyhpndx187yacb",
  "slug": "oo-intercom",
  "version": "1.0.6",
  "publishedAt": 1790160782749
}

skill-card.md

## Description:

This skill helps an agent handle Intercom requests through OOMOL's oo CLI, including reading, creating, updating, and deleting Intercom data.

This skill is ready for commercial/non-commercial use.

## Publisher:

[oomol](https://clawhub.ai/user/oomol)

### License/Terms of Use:

MIT-0

## Use Case:

Support, operations, and engineering teams use this skill to read and manage Intercom workspace data through OOMOL-connected Intercom actions, including contacts, conversations, tickets, articles, tags, events, counts, and admin records.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: Setup instructions include piping remote installer scripts directly into a shell.

Mitigation: Prefer a verified package-manager or installer path, and review any remote script locally before execution.

Risk: Write actions can change Intercom contacts or conversations.

Mitigation: Confirm the exact action, target, payload, and expected effect with the user before execution.

Risk: The close conversation action is destructive.

Mitigation: Require explicit approval for the specific conversation target before running the action.

## Reference(s):

- [ClawHub skill page](https://clawhub.ai/oomol/skills/oo-intercom)
- [OOMOL publisher profile](https://clawhub.ai/user/oomol)
- [oo CLI](https://github.com/oomol-lab/oo-cli)
- [oo CLI install guide](https://cli.oomol.com/install-guide.md)
- [Intercom homepage](https://www.intercom.com)

## Skill Output:

**Output Type(s):** [Shell commands, JSON, Guidance]

**Output Format:** [Markdown with inline shell commands and JSON payloads]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Commands are intended for the OOMOL oo CLI and may return JSON responses from Intercom connector actions.]

## Skill Version(s):

1.0.6 (source: server evidence and frontmatter)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 2d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.

MCPOPENCLAW

Github ReposUpdated 7mo agoRank 70

CopilotKit

The Frontend for Agents & Generative UI. React + Angular