What is the difference between generating a report and rendering a template directly?

Generate Carbone Report renders from a template already stored on the server, referenced by its template ID, with the JSON data supplied at call time. Render Template Direct sends a base64-encoded template and the data together in one request, which suits a one-off document that does not belong in the library.

Which template formats can Lyro render from?

Upload a Template accepts office formats including DOCX, XLSX, and PPTX, so a template stays editable in the tool your team already designs in. The output format is chosen at render time rather than being fixed by the template.

Is deleting a Carbone template reversible?

No. Delete Carbone Template permanently removes a template by its 64-character hexadecimal ID and cannot be undone. Download Template retrieves the original file first, which is worth doing before any deletion that has not been double-checked.

Why would Lyro set the Carbone API version?

Set Carbone API Version fixes the version used for the requests that follow. Pinning it before rendering or managing templates keeps behaviour consistent across a batch instead of leaving it to whichever default the server applies.

Carbone MCP integration

Renders PDFs, Word files, and spreadsheets from templates and live JSON, and keeps the template library uploaded, tagged, and categorised.

Connect Carbone See all integrations

11actions available

Three actions you can hand over today

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

Generate carbone report
Lyro renders a document by combining a Carbone template with data, producing invoices, contracts, reports, or certificates on demand. Output is PDF or image ready.
Render template direct
Lyro generates a document in a single call by uploading a base64-encoded template and data together, skipping the storage step. Useful for one-off renders.
Upload a template
Lyro uploads a document template to Carbone and receives a template ID for future use. This ID can be reused across thousands of renders.

See all 11 actions

How businesses use Carbone + Lyro

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

Produce the document a customer just asked for
Lyro renders a report from a stored template ID and the JSON data behind the request, or uploads a base64-encoded template with its data in one call for a one-off document.
Generate Carbone ReportRender Template Direct
Get a template onto the server and back off it
Lyro uploads a DOCX, XLSX, or PPTX template to obtain the template ID that rendering needs, retrieves the original file when someone needs to edit it, and deletes what is obsolete.
Upload a TemplateDownload TemplateDelete Carbone Template
Find the right template in a growing library
Lyro searches and pages through stored templates, reads the categories that act as folders and the tags in use, and updates a template's name, comment, tags, or category.
List TemplatesList Template CategoriesList Template TagsUpdate Template Metadata
Check the service before a batch runs
Lyro confirms the Carbone server is operational and pins the API version for the requests that follow, so a run of documents does not fail halfway on a version mismatch.
Get Carbone Server StatusSet Carbone API Version

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

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

Carbone · Lyro

Everything else about Carbone

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

Generate Carbone Report renders from a template already stored on the server, referenced by its template ID, with the JSON data supplied at call time. Render Template Direct sends a base64-encoded template and the data together in one request, which suits a one-off document that does not belong in the library.

Every action available in Carbone

All 11 actions your agent can call on Carbone, straight from the live MCP connection.

Delete carbone template
Permanently delete a template from the Carbone server by its 64-character hexadecimal template ID.
Download template
Download a template from Carbone by template ID.
Generate carbone report
Generate a Carbone report from a template and JSON data.
Get carbone server status
Retrieve the current status and health of the Carbone server.
List template categories
Retrieve a list of all categories used in templates.
List templates
Retrieve a list of templates from Carbone storage with filtering, search, and cursor-based pagination.
List template tags
List all tags currently used in templates.
Render template direct
Generate a document by uploading a base64-encoded template and data in a single API call.
Set carbone API version
Set the Carbone API version to be used for subsequent requests.
Update template metadata
Update metadata and attributes of an existing Carbone template.
Upload a template
Upload a template file to the Carbone server to obtain a template ID for document generation.