How does Lyro make sure a new form lands in the right account?

Get User Info returns account and workspace context for the authenticated key but explicitly not form-level access, so it is followed by List Forms to confirm what the key can actually reach. Checking that context before Create Form matters, because acting on the wrong one places the form in an unintended account.

Is there anything from Tally that Lyro should not repeat back?

Get User Info can return sensitive fields such as tokens, and the guidance on that action is not to expose them in user-visible output. Response content from Get Form Responses is fair game for an answer; the account credentials sitting beside it are not.

Which Tally actions are permanent?

Delete Form removes a form permanently and Delete Webhook removes a callback outright, with no archive step behind either. Update Webhook carries an enable and disable status, so pausing deliveries is the reversible alternative when something is only temporarily wrong.

Can Lyro see webhooks across every form at once?

Yes. List Webhooks returns a paginated listing across all the forms and workspaces the authenticated user can reach rather than being scoped to one form, which makes it the right starting point when submissions stopped arriving and nobody remembers which form the callback was attached to.

Tally MCP integration

Reads form responses and the questions behind them, builds and edits forms from block definitions, and wires submissions out through webhooks.

Connect Tally See all integrations

18actions available

Three actions you can hand over today

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

Create form
Lyro sets up a new form instantly during a support conversation. Customers can gather feedback or data collection needs without waiting for manual setup.
Get form details
Lyro pulls the full configuration and metadata of a form. Teams verify form settings or describe capabilities to customers without navigating the UI.
Get form responses
Lyro fetches all responses submitted to a specific form. Agents review customer feedback or form data to answer questions or identify patterns in a single lookup.

See all 18 actions

How businesses use Tally + Lyro

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

Answer from a form's actual responses
Lyro pages through a form's responses and reads the question list they map onto, plus the form's full configuration, blocks, and stats when the answer depends on how it was built.
Get Form ResponsesList Form QuestionsGet Form Details
Stand up or amend a form on request
Lyro creates a form from prepared block definitions and settings, edits an existing one after confirming its ID, and permanently removes a form that is no longer wanted.
Create FormUpdate FormDelete Form
Push every new submission into your own systems
Lyro registers a webhook against a form and callback URL, changes its URL, event types, or enabled status later, and inspects the delivery history when something stopped arriving.
Create WebhookUpdate WebhookGet Webhook Events
Check who can reach which workspace
Lyro lists the workspaces the account can see, opens one with its members, and reports the organization's users along with any invitations still waiting to be accepted.
List WorkspacesGet WorkspaceList Organization Users

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 Tally actions it has and picks the ones a request needs.

01
Connect Tally
Authorize the Tally 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 Tally 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

Tally · Lyro

Everything else about Tally

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

Get User Info returns account and workspace context for the authenticated key but explicitly not form-level access, so it is followed by List Forms to confirm what the key can actually reach. Checking that context before Create Form matters, because acting on the wrong one places the form in an unintended account.

Every action available in Tally

All 18 actions your agent can call on Tally, straight from the live MCP connection.

Create form
Create a new form.
Create webhook
Create a new webhook for a form.
Delete form
Delete a specific form identified by its ID.
Delete webhook
Delete a specific webhook.
Get form details
Retrieve details of a specific form.
Get form responses
Retrieve the responses of a specific form.
Get user info
Retrieve information about the authenticated user.
Get webhook events
List events associated with a specific webhook.
Get workspace
Retrieve a single workspace by its ID with associated members.
List form questions
Retrieve all questions from a specific form.
List forms
Retrieve a paginated list of forms.
List organization invites
Retrieve all pending invites in your organization.
List organization users
Retrieve all users in an organization.
List webhooks
Retrieve a paginated list of configured webhooks.
List workspaces
Retrieve a paginated list of workspaces.
Update form
Update form details.
Update webhook
Update an existing webhook configuration.
Update workspace
Update the details of a specific workspace identified by its ID.