2Chat

2Chat (2chat.co). Use this skill for ANY 2Chat request — reading, creating, and updating data. Whenever a task involves 2Chat, use this skill instead of calling the API directly.

Operate 2Chat through your OOMOL-connected account. This skill calls the twochat connector with the 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 2Chat. 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:

bash

oo connector schema "twochat" --action "<action_name>"

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

bash

oo connector run "twochat" --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

• create_contact — Create a contact in 2Chat with one or more contact details and optional channel and profile picture metadata. [write]
• get_api_usage_info — Fetch the current 2Chat account, rate limit, and usage counters for the connected API key.
• list_contacts — List contacts from the connected 2Chat account, with optional pagination and channel filtering.
• list_webhooks — List the webhook subscriptions currently configured in the connected 2Chat account.
• test_api_key — Validate the connected 2Chat API key and return normalized account, limit, and usage information.

Safety

• Untagged actions are reads (get / list / search) — safe to run directly.
• Actions tagged [write] change 2Chat state — confirm the exact payload and effect with the user before running.
• Actions tagged [destructive] remove or overwrite data — 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: https://cli.oomol.com/install-guide.md):

  bash

  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  

  powershell

  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  

• Not signed in / authentication error — sign in to your OOMOL account once:

  bash

  oo auth login
  

• scope_missing / credential_expired / app_not_ready / app_not_found — 2Chat is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

  text

  https://console.oomol.com/app-connections?provider=twochat
  

• HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

• 2Chat homepage: https://2chat.co