# Kintone integrations: records, apps and files

> Add records, add a preview app and upload a file in Kintone, and start a workflow when Kintone sends “Record added”.

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

## Overview

Kintone is a no-code platform from Cybozu for building business database apps, with records, process management, comments and shared team spaces. Tray.ai connects to Kintone through the HTTP Connector, so your workflows can call the Kintone API alongside the rest of your stack.

## Use cases

### Records

Read, create, update, and delete records in Kintone from any Tray.ai workflow. The Kintone API covers calls such as get records and add records.

- Get records
- Add records
- Update records

### Apps

Read, create, and update apps in Kintone from any Tray.ai workflow. The Kintone API covers calls such as get apps and add a preview app.

- Get apps
- Add a preview app
- Deploy app settings

### Files

Read and create files in Kintone from any Tray.ai workflow. The Kintone API covers calls such as upload a file and download a file.

- Upload a file
- Download a file

### Spaces

Read, create, update, and delete spaces in Kintone from any Tray.ai workflow. The Kintone API covers calls such as get a space and add a space from a template.

- Get a space
- Add a space from a template
- Update space members

### Kintone events

Start a Tray.ai workflow the moment something happens in Kintone. Kintone sends events such as record added and record edited to a Tray.ai webhook trigger.

- Record added
- Record edited
- Record deleted

## Challenges Tray.ai solves

### Keeping Kintone 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 Kintone 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 Kintone 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 Kintone 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 Kintone?

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

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

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

### Can I get a dedicated Kintone connector?

Kintone runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Kintone connector from the Kintone 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/