Byteforms logo
ConnectorByteforms

Byteforms integration for Claude and Codex

Create a Byteforms connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.

Use Byteforms from Claude

Add the Byteforms connection to a Space that runs Claude, then use it from every channel in that Space.

Use Byteforms from Codex

Add the Byteforms connection to a Space that runs Codex, then use it from every channel in that Space.

Use Byteforms from Sidekick

Connect your own OpenClaw to Sidekick while Type provides the conversations, permissions, connections, skills, and automations.

Documents & Forms

What the Byteforms connector can do

All-in-one solution for form creation, submission management, and data integration.

One connection, many Spaces

Connect Byteforms once, then decide which Spaces can use it in threads, skills, automations, and coding work.

Representative actions

  • Create form

    Creates a new form in ByteForms. Use this to build data collection forms with customizable fields (text, email, phone), styling options (theme, width), and submission rules (limits, deadlines, password protection). Returns the created form with its public_id for sharing.

  • Delete Form

    Tool to delete a form by its ID. Use when you need to remove an existing form permanently.

  • Get All Forms

    Tool to fetch all forms created by the authenticated user. Use after authentication to list existing forms.

  • Get Form By ID

    Retrieves detailed information about a specific form by its numeric ID. Returns the form's name, fields, configuration options, and metadata. Use the numeric 'id' field (not the 'public_id' string) from form data obtained via BYTEFORMS_GET_ALL_FORMS or BYTEFORMS_CREATE_FORM.

  • Get Form Responses

    Tool to retrieve responses for a specific form with optional pagination and filtering. Use when the form has collected submissions and you need to navigate large result sets.

Connection

API and auth details

ByteForms public integration documentation describes form APIs for listing forms, retrieving a specific form, and getting form responses by form ID. Public search surfaces limited vendor-hosted endpoint documentation, so integrations should treat ByteForms as a form and response-data source with available public examples rather than assuming a broad documented API surface.

FAQ

Questions people ask before connecting Byteforms

Can Claude use Byteforms?

Yes. Add a Byteforms connection to a Space that runs Claude, then use its approved tools and data from any channel in that Space.

Can Codex work with Byteforms through Type?

Yes. Add a Byteforms connection to a Space that runs Codex, then use its approved tools and data from any channel in that Space.

Is this the same as a Byteforms MCP server?

Not exactly. Type uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.

More documents & forms connectors