# Formstack Documents integrations: documents

> Create a document, create a data route and create a document delivery in Formstack Documents.

**Canonical page:** https://tray.ai/connectors/formstack-documents-integrations/
**Categories:** Documents and e-signature
**Connects through:** HTTP Connector

## Overview

Formstack Documents, formerly WebMerge, fills document templates with data to produce contracts, letters and other files, then delivers them by email, storage or e-signature. Tray.ai connects to Formstack Documents through the HTTP Connector, so your workflows can call the Formstack Documents API alongside the rest of your stack.

## Use cases

### Documents

Read, create, update, and delete documents in Formstack Documents from any Tray.ai workflow. The Formstack Documents API covers calls such as list documents and create a document.

- List documents
- Create a document
- Update a document

### Data Routes

Read, create, update, and delete data routes in Formstack Documents from any Tray.ai workflow. The Formstack Documents API covers calls such as list data routes and create a data route.

- List data routes
- Create a data route
- Update a data route

### Deliveries

Read and create deliveries in Formstack Documents from any Tray.ai workflow. The Formstack Documents API covers calls such as list document deliveries and create a document delivery.

- List document deliveries
- Create a document delivery

## Challenges Tray.ai solves

### Keeping Formstack Documents 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 Formstack Documents 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 Formstack Documents 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 Formstack Documents 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 Formstack Documents?

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

### How does Tray.ai authenticate with Formstack Documents?

The Formstack Documents API uses basic authentication. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Formstack Documents connector?

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