Jotform

SKILL.md

---
name: oo-jotform
description: "Jotform (jotform.com). Use this skill for ANY Jotform request — reading, creating, and updating data. Whenever a task involves Jotform, use this skill instead of calling the API directly."
allowed-tools: [Bash(oo *)]
metadata:
  title: "Jotform"
  author: "OOMOL"
  version: "1.0.0"
  service: "jotform"
  categories: "Productivity, Data & Analytics"
  homepage: "https://www.jotform.com"
  icon: "https://static.oomol.com/logo/third-party/Jotform.svg"
---

# Jotform

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

Category: Productivity, Data & Analytics. Exposes 7 action(s).

## Running an action

Assume the user has already installed the oo CLI, signed in, and connected Jotform. **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 "jotform" --action "<action_name>"
```

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

```bash
oo connector run "jotform" --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 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

- [`create_submission`](actions/create_submission.md) — Create a submission on a Jotform form using question IDs and answer values.
- [`get_current_user`](actions/get_current_user.md) — Get the current Jotform account associated with the authenticated API key.
- [`get_form`](actions/get_form.md) — Get one Jotform form by form ID.
- [`get_submission`](actions/get_submission.md) — Get one Jotform submission by submission ID.
- [`list_form_questions`](actions/list_form_questions.md) — List the question definitions configured on one Jotform form.
- [`list_form_submissions`](actions/list_form_submissions.md) — List submissions for one Jotform form.
- [`list_forms`](actions/list_forms.md) — List forms available to the authenticated Jotform account.

## Safety

- Read actions (get / list / search) are safe to run directly.
- **Create, update, send, or post actions change Jotform 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: <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`** — Jotform 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=jotform
  ```

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

## Resources

- Jotform homepage: https://www.jotform.com