Use Byteforms from Claude
Add the Byteforms connection to a Space that runs Claude, then use it from every channel in that Space.
Create a Byteforms connection, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the Byteforms connection to a Space that runs Claude, then use it from every channel in that Space.
Add the Byteforms connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
ByteForms is a form builder for collecting data with customizable fields, styling, and submission rules like deadlines or password protection. A type.com Space can have Claude build a new form, check an existing form's configuration, or pull in the responses a form has collected so far.
Connect Byteforms once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Create a form with the fields and submission rules a team needs, instead of configuring it manually in the ByteForms editor.
Create a ByteForms intake form with name, email, and phone fields, limited to 200 submissions.
Pull a specific form's fields and settings by ID to confirm what's live before making changes.
Get the ByteForms form details for form ID 118 before we add a new field.
Fetch a form's collected responses, with pagination for larger forms, to summarize results without exporting a spreadsheet.
Get the responses for our ByteForms event signup form and summarize how many people signed up this week.
Builds a new ByteForms form with custom fields, styling, and submission rules like limits or deadlines.
Permanently removes a form by its ID.
Lists every form created by the authenticated account.
Retrieves a form's fields, configuration, and metadata using its numeric ID.
Retrieves a form's collected responses, with pagination and filtering for forms with many submissions.
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.
Yes. With a ByteForms connection shared to your Space, Claude can create forms, check their configuration, and pull responses directly in a thread.
ByteForms uses an API key you add once to the connection, managed by an admin who controls which Spaces can use it.
Yes. Set up a type.com automation to pull new ByteForms responses weekly and post a summary to a channel.
Not exactly. type.com 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.
Connect Signaturely to Claude in type.com to organize signing folders, check recent documents, and list pending signatures in a thread.
Connect Signwell to Claude in type.com to send documents for signature, generate them from templates, and manage webhooks in a thread.
Connect Slite to Claude in type.com to ask questions against your notes, create documentation, and flag outdated content in a shared thread.
Connect Spondyr to Claude in type.com to set up template conditions, register transaction types, and trigger correspondence from a shared thread.