# Loopio integrations

> Call the Loopio API from any Tray.ai workflow with the HTTP Connector.

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

## Overview

Loopio is RFP response software that keeps a shared library of approved answers and runs response projects for RFPs, security questionnaires, and proposals. Tray.ai connects to Loopio through the HTTP Connector, so your workflows can call the Loopio API alongside the rest of your stack.

## Use cases

### Library entries

Read, create, and update library entries in Loopio from any Tray.ai workflow. The Loopio API covers calls such as search library entries and get a library entry.

- Search library entries
- Get a library entry
- Create a library entry

### Projects

Read, create, and update projects in Loopio from any Tray.ai workflow. The Loopio API covers calls such as search projects and get a project.

- Search projects
- Get a project
- Create a project

### Project sections

Read and create project sections in Loopio from any Tray.ai workflow. The Loopio API covers calls such as create a project section and get project compliance sets.

- Create a project section
- Get project compliance sets

### Users

Read users in Loopio from any Tray.ai workflow. The Loopio API covers calls such as list users and get a user.

- List users
- Get a user

## Challenges Tray.ai solves

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

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

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

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

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