AccuLynx

Operate AccuLynx through your OOMOL-connected account. This skill calls the acculynx 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 AccuLynx. 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 "acculynx" --action "<action_name>"

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

oo connector run "acculynx" --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 one new contact in AccuLynx. [write]
• create_job — Create one new job in the AccuLynx Lead milestone. [write]
• get_company_settings — Get the current AccuLynx company settings for the connected location.
• get_initial_appointment — Get the initial appointment for one AccuLynx job.
• list_calendar_appointments — List appointment summaries for one AccuLynx calendar within a date range.
• list_calendars — List the calendars available in the current AccuLynx location.
• list_contact_types — List the contact types configured for the current AccuLynx company.
• list_job_categories — List the active AccuLynx job categories configured for the company.
• list_lead_sources — List the active lead sources configured for the current AccuLynx company.
• list_trade_types — List the active AccuLynx trade types configured for the company.
• list_work_types — List the active AccuLynx work types configured for the company.
• upsert_initial_appointment — Add or update the initial appointment for one AccuLynx job. [write]

Safety

• Untagged actions are reads (get / list / search) — safe to run directly.
• Actions tagged [write] change AccuLynx 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: ):

```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 — AccuLynx 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=acculynx

```

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

Resources

• AccuLynx homepage: https://acculynx.com