Can Lyro generate an image or PDF from a Placid template?

No. The connected actions manage templates and collections; there is no render call in this toolkit. Lyro finds the right template and returns its UUID and layer list, which is what your own rendering request or Placid automation needs to produce the asset.

Does deleting a collection delete the templates inside it?

No. Delete Collection removes the grouping only and the templates stay in the project, which is documented behaviour rather than a side effect. Removing a template itself takes Delete Template with that template's UUID.

How does Lyro work through a large template library?

List Templates returns 20 items per page with cursor pagination and accepts a collection or title filter, so Lyro narrows by campaign or name instead of paging through everything. Get Template then returns the full layer detail for whichever one matched.

What is the Natural Language template list for?

List NL Templates returns the templates exposed through Placid's Natural Language API, the route used when an image is described rather than named by UUID. Lyro reads that list when the goal is a described image, and List Templates when it needs the full project library with layers.

Placid MCP integration

Browses templates with their layers and tags, creates new ones at set dimensions, and groups them into collections with custom metadata.

Connect Placid See all integrations

11actions available

Three actions you can hand over today

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

Get template
Lyro fetches a template by UUID. Support accesses the template configuration for customization or technical review.
List templates
Lyro retrieves all templates from the Placid project. Support browses available image templates for customer selection.
Update template
Lyro updates an existing Placid template's properties. Support adapts templates for new customer requirements or branding.

See all 11 actions

How businesses use Placid + Lyro

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

Find the right template before anything is rendered
Lyro pages through the project's templates 20 at a time, filtered by collection or title, and returns a template's thumbnail, tags and layers so the correct UUID reaches whatever renders the asset.
List TemplatesGet TemplateList NL Templates
Create a template at the size a channel needs
Lyro creates a Placid template with the dimensions requested plus any tags or custom metadata, then revises its title or tags later without anyone opening the editor.
Create TemplateUpdate TemplateGet Template
Group templates into a collection per campaign
Lyro creates a collection with its title and custom data, then manages membership by replacing the whole set or adding and removing individual templates as the campaign changes.
Create CollectionUpdate CollectionGet Collections
Retire templates and collections that are done
Lyro reads a collection's title, custom data and associated template UUIDs back before deleting it, and removes individual templates by UUID once nothing depends on them.
Get CollectionDelete CollectionDelete Template

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

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

Placid · Lyro

Everything else about Placid

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

No. The connected actions manage templates and collections; there is no render call in this toolkit. Lyro finds the right template and returns its UUID and layer list, which is what your own rendering request or Placid automation needs to produce the asset.