TicketSource Connector for Openclaw

The normal workflow assumes the oo CLI is already installed, the user is signed in, and TicketSource is connected. Do not run login or open the connection page proactively; use these steps only when the matching error occurs.

Install the OOMOL CLI if oo is unavailable:

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

On Windows PowerShell:

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

Sign in once after an authentication error:

oo auth login

Connect or reconnect TicketSource when the CLI reports scope_missing, credential_expired, app_not_ready, or app_not_found. Use the OOMOL connection page and select API key authentication:

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

For HTTP 402 or OOMOL_INSUFFICIENT_CREDIT, recharge OOMOL billing credits before retrying. Once setup succeeds, return to the schema inspection and connector execution workflow used by these Openclaw Skills.

Connector identity

Request structure

• Inspect each action with oo connector schema "ticket_source" --action "<action_name>" before creating input data.
• Pass a JSON object through --data '<json>', or provide a JSON file with --data @path/to/file.json.
• Omit --data when the action accepts an empty object {}.
• Event identifiers are case-sensitive where required by get_event and related event-specific actions.

Response envelope

{
  "data": "<action-specific result>",
  "meta": {
    "executionId": "<oomol-execution-id>"
  }
}

The data property contains the action-specific TicketSource result. The meta.executionId value provides execution tracing metadata. The skill does not define a local database or generated project files; results are returned directly as JSON for the calling agent or automation.