Which ByteForms identifier does Lyro need to look up a form?

The numeric id, not the public_id string. Get Form By ID takes the numeric identifier returned by Get All Forms or Create Form, while public_id is the value that appears in the form's shareable URL, so Lyro resolves the numeric one first when someone refers to a form by its link or by name.

Can Lyro submit an entry to a ByteForms form for a customer?

No. The connected actions cover creating, inspecting, and deleting forms and reading their responses, with no submit action among them. Lyro shares the form from Create Form so the customer fills it in themselves, then reads what arrives with Get Form Responses.

Which forms can Lyro see in ByteForms?

Only the ones belonging to the account you connect. Get All Forms fetches forms created by the authenticated user, so a form built under a colleague's ByteForms login stays invisible until that account is connected as well.

How does Lyro avoid deleting a ByteForms form by mistake?

Delete Form removes a form permanently and the toolkit has no restore action, so Lyro resolves the name someone used through Get All Forms and confirms the match before calling it. Reading the entries with Get Form Responses first is the safer order, since the submissions go with the form.

Byteforms MCP integration

Builds forms with the fields and submission rules described in chat, returns the shareable ID, pages through responses, and retires old forms.

Connect Byteforms See all integrations

5actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

Get form responses
Lyro retrieves all customer responses to a form with optional filtering and pagination. Your team pulls submission data without logging into ByteForms.
Create form
Lyro creates a new form in ByteForms during a conversation. Your team instantly deploys surveys or feedback forms without leaving chat.
Get form by ID
Lyro fetches full form details including structure and metadata. Your team verifies form configuration or troubleshoots submission problems.

See all 5 actions

How businesses use Byteforms + Lyro

Each card is one request a support team gets, and the Byteforms actions Lyro runs to close it.

Create a form from a plain-language brief
Lyro builds the form with the text, email, and phone fields asked for, applies the theme, width, submission limit, deadline, or password rule, and hands back the public_id used to share it.
Create FormGet Form By IDGet All Forms
Pull submissions without opening the dashboard
Lyro retrieves a form's responses with pagination and filtering, so a question about what came in this week is answered from the live submission set instead of an exported spreadsheet.
Get Form ResponsesGet All FormsGet Form By ID
Check how a live form is configured
Lyro reads a specific form's fields, configuration options, and metadata by its numeric ID, so a question about which fields are required or whether the deadline has passed gets a current answer.
Get Form By IDGet All FormsGet Form Responses
Retire forms that have run their course
Lyro matches the form someone names against everything in the account, confirms the match, and deletes it, so a finished campaign stops collecting entries nobody is reading.
Get All FormsGet Form By IDDelete Form

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Byteforms actions it has and picks the ones a request needs.

01
Connect Byteforms
Authorize the Byteforms account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Byteforms actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Byteforms · Lyro

Everything else about Byteforms

Setup, permissions, and the limits of what Lyro can do inside Byteforms.

The numeric id, not the public_id string. Get Form By ID takes the numeric identifier returned by Get All Forms or Create Form, while public_id is the value that appears in the form's shareable URL, so Lyro resolves the numeric one first when someone refers to a form by its link or by name.

Every action available in Byteforms

All 5 actions your agent can call on Byteforms, straight from the live MCP connection.

Create form
Creates a new form in ByteForms.
Delete form
Delete a form by its ID.
Get all forms
Fetch all forms created by the authenticated user.
Get form by ID
Retrieves detailed information about a specific form by its numeric ID.
Get form responses
Retrieve responses for a specific form with optional pagination and filtering.