# 123FormBuilder integrations

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

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

## Overview

123FormBuilder is an online form builder for creating web forms and surveys, collecting submissions, and sharing forms across user groups. Tray.ai connects to 123FormBuilder through the HTTP Connector, so your workflows can call the 123FormBuilder API alongside the rest of your stack.

## Use cases

### Forms

Read, create, update, and delete forms in 123FormBuilder from any Tray.ai workflow. The 123FormBuilder API covers calls such as list forms and get form details.

- List forms
- Get form details
- Create a form

### Submissions

Read, update, and delete submissions in 123FormBuilder from any Tray.ai workflow. The 123FormBuilder API covers calls such as list form submissions and get a submission.

- List form submissions
- Get a submission
- Update a submission

### Groups

Read, create, and update groups in 123FormBuilder from any Tray.ai workflow. The 123FormBuilder API covers calls such as list groups and create a group.

- List groups
- Create a group
- Update a group

### Users

Read, create, and update users in 123FormBuilder from any Tray.ai workflow. The 123FormBuilder API covers calls such as list users and create a subuser.

- List users
- Create a subuser
- Update a user

## Challenges Tray.ai solves

### Keeping 123FormBuilder 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 123FormBuilder 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 123FormBuilder 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 123FormBuilder 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 123FormBuilder?

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

### How does Tray.ai authenticate with 123FormBuilder?

The 123FormBuilder API uses a token in the request URL. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated 123FormBuilder connector?

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