← Back to Skills Marketplace
🔌

Intercom

by OOMOL · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
38
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install oo-intercom
Description
Intercom (intercom.com). Use this skill for ANY Intercom request — reading, creating, and updating data. Whenever a task involves Intercom, use this skill in...
README (SKILL.md)

Intercom

Operate Intercom through your OOMOL-connected account. This skill calls the intercom connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Category: Communication, Productivity. Exposes 14 action(s).

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 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:

oo connector schema "intercom" --action "\x3Caction_name>"

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

oo connector run "intercom" --action "\x3Caction_name>" --data '\x3Cjson>' --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 below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with oo connector schema before constructing --data.

Available actions

Safety

  • Read actions (get / list / search) are safe to run directly.
  • Create, update, send, or post actions change Intercom state — confirm the exact payload and effect with the user before running.
  • Delete or remove actions are destructive — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: \x3Chttps://cli.oomol.com/install-guide.md>):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
    
    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
    
  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login
    
  • scope_missing / credential_expired / app_not_ready / app_not_found — Intercom is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:

    https://console.oomol.com/app-connections?provider=intercom
    
  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

Usage Guidance
Install this only if you intend to let an agent use your connected Intercom workspace through OOMOL. Read/list/search actions can expose customer, admin, and conversation data, and write actions can create contacts, update records, reply to users, or close/reopen conversations, so keep the confirmation requirement enabled for any state-changing request.
Capability Assessment
Purpose & Capability
The skill is explicitly for operating Intercom through the OOMOL oo CLI, with documented actions for contacts, conversations, and admins; the read and write capabilities match that stated purpose.
Instruction Scope
The manifest says to use the skill for any Intercom request, which is broad, but the action set is Intercom-specific and the instructions require live schema inspection and user confirmation before create, update, reply, close, or reopen actions.
Install Mechanism
There is no bundled executable code; the only install guidance is a conditional first-time oo CLI install using OOMOL-hosted shell or PowerShell commands if the CLI is missing.
Credentials
Allowed tooling is limited to Bash commands matching oo usage, and the skill does not request broad filesystem, credential-store, or unrelated environment access.
Persistence & Privilege
The skill may rely on a persistent OOMOL login and connected Intercom OAuth account, but it tells the agent not to initiate login or connection setup proactively and says raw Intercom tokens are injected server-side rather than handled by the skill.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install oo-intercom
  3. After installation, invoke the skill by name or use /oo-intercom
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Adds an OOMOL-powered Intercom skill for working with an already connected Intercom workspace through the `oo` CLI. - Supports contact workflows including create, update, list, search, lookup by ID, and lookup by external ID. - Supports conversation workflows including list, fetch with conversation parts, reply as an admin, close, and reopen. - Provides admin and workspace access through current-admin lookup, admin lookup, and admin listing actions. - Documents safe execution patterns, live schema inspection before payload construction, and confirmation requirements for write actions.
Metadata
Slug oo-intercom
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Intercom?

Intercom (intercom.com). Use this skill for ANY Intercom request — reading, creating, and updating data. Whenever a task involves Intercom, use this skill in... It is an AI Agent Skill for Claude Code / OpenClaw, with 38 downloads so far.

How do I install Intercom?

Run "/install oo-intercom" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Intercom free?

Yes, Intercom is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Intercom support?

Intercom is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Intercom?

It is built and maintained by OOMOL (@oomol); the current version is v1.0.0.

💬 Comments