# TrackVia integrations: apps, views and records

> Add a record in TrackVia. Connect TrackVia to the rest of your operations stack with Tray.ai.

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

## Overview

TrackVia is a low-code platform for building custom business apps on top of tables, views, and records, often used for field operations and work tracking. Tray.ai connects to TrackVia through the HTTP Connector, so your workflows can call the TrackVia API alongside the rest of your stack.

## Use cases

### Apps

Read apps in TrackVia from any Tray.ai workflow. The TrackVia API covers calls such as list apps and get an app by name.

- List apps
- Get an app by name

### Views

Read views in TrackVia from any Tray.ai workflow. The TrackVia API covers calls such as list views and get a view by name.

- List views
- Get a view by name
- Get view records

### Records

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

- Get a record
- Add a record
- Update a record

### Files

Read and delete files in TrackVia from any Tray.ai workflow. The TrackVia API covers calls such as get a file and attach a file.

- Get a file
- Attach a file
- Delete a file

### Users

Read and create users in TrackVia from any Tray.ai workflow. The TrackVia API covers calls such as list users and add a user.

- List users
- Add a user

## Challenges Tray.ai solves

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

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

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

The TrackVia API uses 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 TrackVia connector?

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