Integration

Clappia integration

Clappia is a no-code platform for building business apps (forms, inspections, field data collection) whose records are called submissions. List the workplace's apps, then create, edit, read, list, filter, sort and count an app's submissions, change their status and set their owners. Creating or editing a submission acts in the live app, as a user submission does. Not exposed: app design (fields, sections, pages, versions, metadata), workflow and chart definitions, workplace user management, file upload and download links, Excel export and bulk upload, and aggregations. Every workplace API key starts at 1,000 API calls per month, on the free plan too; paid plans can buy more as REST API add-ons. Some errors (an invalid app ID, submission ID, field or filter) come back with HTTP 200 and only an error field. Authentication: a workplace API key (Workplace Settings, Preferences, API Keys) sent in the x-api-key header; most tools also take your workplace ID from Workplace Settings.

Connect Clappia How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Clappia.Built from the 8 Clappia tools below, on the connection you add once.

What you can do with Clappia

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Submission, 5 operations

count_submissionsCount submissionsPOSTCounts a Clappia app's submissions: totalCount and filteredCount for the optional filter tree (same as list_submissions). Errors come back with HTTP 200 in the error field.
create_submissionCreate submissionPOSTCreates a new submission (record) in a Clappia app as the given workplace user. Field keys in data are the app's field variable names. Returns submissionId. Errors may come back in the error field.
edit_submissionEdit submissionPOSTUpdates field values of an existing Clappia submission. Keys in data are the app's field variable names (see submissionFieldValues in get_submission). Changes the live record. Errors come back in the error field.
get_submissionGet submissionGETReturns one Clappia submission: field values keyed by field variable name, status, owners, creator and last editor. Errors (invalid app or submission ID) come back with HTTP 200 in the error field.
list_submissionsList submissionsPOSTLists a Clappia app's submissions a page at a time (filters, sort, field choice). For the next page pass the answer's lastSubmissionId with forward true. Errors come back with HTTP 200 in error.

App, 1 operation

list_workplace_appsList workplace appsGETLists the Clappia workplace's apps with appId, name, creation and update times and who created or last updated each. Start here to find the appId. Errors may come back in the error field.

Submission owner, 1 operation

update_submission_ownersUpdate submission ownersPOSTSets a Clappia submission's owners to the given workplace users' email addresses, changing who can see and act on the record. Errors may come back with HTTP 200 in the error field.

Submission status, 1 operation

update_submission_statusUpdate submission statusPOSTSets a Clappia submission's status to one configured in the app, with an optional comment. Changes the live record; a status the app does not define is refused in the error field.

Use Clappia from Claude Code, Cursor or Codex

Connect Clappia in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Clappia operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Clappia

Create your workspace
Sign up free. Nothing to install.
Connect Clappia once
Add your Clappia connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.