# FormAssembly integrations: forms and responses

> Create a form, export form responses and create a connector in FormAssembly. Connect FormAssembly to the rest of your operations stack with Tray.ai.

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

## Overview

FormAssembly is an online form builder for collecting data through web forms, with form responses exportable and sent on to other systems through connectors. Tray.ai connects to FormAssembly through the HTTP Connector, so your workflows can call the FormAssembly API alongside the rest of your stack.

## Use cases

### Forms

Read, create, update, and delete forms in FormAssembly from any Tray.ai workflow. The FormAssembly API covers calls such as list forms and view a form.

- List forms
- View a form
- Create a form

### Responses

Read responses in FormAssembly from any Tray.ai workflow. The FormAssembly API covers calls such as export form responses and filter responses by date.

- Export form responses
- Filter responses by date

### Connectors

Read, create, update, and delete connectors in FormAssembly from any Tray.ai workflow. The FormAssembly API covers calls such as list connectors and view a connector.

- List connectors
- View a connector
- Create a connector

### Themes

Read, create, update, and delete themes in FormAssembly from any Tray.ai workflow. The FormAssembly API covers calls such as list themes and view a theme.

- List themes
- View a theme
- Create a theme

## Challenges Tray.ai solves

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

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

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

The FormAssembly 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 FormAssembly connector?

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