Which Pylon user does Lyro act as?

The user behind the credentials you connect. Get Me returns that user's name, email, role, and teams, and every issue Lyro creates or updates is attributed to it, so the audit trail in Pylon shows the integration rather than an anonymous API call.

What does Lyro need before it can open an issue?

Create Issue requires an organization ID, an account ID, a title, and body HTML. Requester, priority, assignee, and tags are optional, which is why Lyro resolves the customer with Search Accounts or Get Contact before filing rather than opening an unattached ticket.

Can Lyro set our own custom fields on an account?

Yes, Update Account covers name, owner, tags, and custom fields. The field definitions come from Pylon's custom field lookup for that object type, so Lyro writes into fields your team already defined and cannot invent a new one.

Are there limits on files Lyro attaches to an account?

Upload Account Files takes at most five files per call with a 10 MB ceiling, and a file whose name matches an existing one overwrites it. That overwrite behaviour is useful for keeping a single current contract on the account, and worth knowing before uploading versioned documents.

Pylon MCP MCP integration

Answers status questions from live issue history, opens issues with requester and priority set, and keeps state, assignee, and tags current.

Connect Pylon MCP See all integrations

12actions available

Three actions you can hand over today

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

Create issue
Lyro opens a new support issue or ticket in Pylon from any channel. Support requests flow directly into Pylon without manual ticket creation.
Update issue
Lyro edits an existing Pylon issue to change status, priority, or notes. Support teams move tickets through workflow without Pylon login.
Search accounts
Lyro finds customer accounts in Pylon by query to retrieve their full context. Agents look up accounts instantly without scrolling through lists.

See all 12 actions

How businesses use Pylon MCP + Lyro

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

Answer a status question from the live issue
Lyro finds the issue by number or filter, reads its state and metadata, and works through the message history in order, so a customer hears where their request actually stands.
Search IssuesGet IssueGet Issue Messages
Open a Pylon issue from the conversation
Lyro resolves the contact and their account first, then creates the issue with a title, body, requester, and priority already filled in rather than a bare one-line ticket.
Create IssueGet ContactGet Account
Route and tag the queue as work moves
Lyro updates issue state, assignee, team, and tags, keeps the account's owner and custom fields in step, and checks a team member's role before assigning work to them.
Update IssueUpdate AccountGet User
Keep account context where the team looks for it
Lyro searches accounts by name, domain, or custom field, and files a PDF into the account's Files tab, so the document sits on the record instead of in someone's inbox.
Search AccountsUpload Account FilesGet Account

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

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

Pylon MCP · Lyro

Everything else about Pylon MCP

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

The user behind the credentials you connect. Get Me returns that user's name, email, role, and teams, and every issue Lyro creates or updates is attributed to it, so the audit trail in Pylon shows the integration rather than an anonymous API call.