# Clappia integrations: submissions

> Create a submission, create an app version and add a user to the workplace in Clappia. Connect Clappia to the rest of your operations stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/clappia-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

Clappia is a no-code platform for building business apps such as forms, inspections and field data collection, with workflows, charts and offline mobile use. Tray.ai connects to Clappia through the HTTP Connector, so your workflows can call the Clappia API alongside the rest of your stack.

## Use cases

### Submissions

Read, create, and update submissions in Clappia from any Tray.ai workflow. The Clappia API covers calls such as create a submission and edit a submission.

- Create a submission
- Edit a submission
- Update submission status

### App definitions

Read, create, and update app definitions in Clappia from any Tray.ai workflow. The Clappia API covers calls such as get an app definition and add a field.

- Get an app definition
- Add a field
- Update a field

### Workplace users

Read, create, and update workplace users in Clappia from any Tray.ai workflow. The Clappia API covers calls such as add a user to the workplace and update user details.

- Add a user to the workplace
- Update user details
- Add a user to an app

### Files

Create files in Clappia from any Tray.ai workflow. The Clappia API covers calls such as generate a file upload URL and generate a file download URL.

- Generate a file upload URL
- Generate a file download URL

### Bulk uploads

Read and create bulk uploads in Clappia from any Tray.ai workflow. The Clappia API covers calls such as import a bulk upload Excel and get bulk upload status.

- Import a bulk upload Excel
- Get bulk upload status

## Challenges Tray.ai solves

### Keeping Clappia credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Clappia credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Clappia API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Clappia API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Clappia?

Yes. Tray.ai connects to Clappia through the HTTP Connector, which calls the Clappia API directly. Any call the Clappia API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Clappia?

The Clappia API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Clappia connector?

Clappia runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Clappia connector from the Clappia API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/