# Ragic integrations: records and record actions

> Create a record, add a comment and upload a file in Ragic, and start a workflow when Ragic sends “Record created”.

**Canonical page:** https://tray.ai/connectors/ragic-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Ragic is a no-code database builder that works like a spreadsheet, letting teams design sheets and forms for records such as orders, inventory and customers. Tray.ai connects to Ragic through the HTTP Connector, so your workflows can call the Ragic API alongside the rest of your stack.

## Use cases

### Records

Read, create, update, and delete records in Ragic from any Tray.ai workflow. The Ragic API covers calls such as list records and get a record.

- List records
- Get a record
- Create a record

### Record actions

Create and update record actions in Ragic from any Tray.ai workflow. The Ragic API covers calls such as lock a record and add a comment.

- Lock a record
- Add a comment
- Run an action button

### Files

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

- Upload a file
- Download a file

### Sheets

Read and manage sheets in Ragic from any Tray.ai workflow. The Ragic API covers calls such as get a sheet schema and mass update records.

- Get a sheet schema
- Mass update records

### Ragic events

Start a Tray.ai workflow the moment something happens in Ragic. Ragic sends events such as record created and record updated to a Tray.ai webhook trigger.

- Record created
- Record updated
- Record deleted

## Challenges Tray.ai solves

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

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

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

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

### Can I get a dedicated Ragic connector?

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