Carbone

Transforms raw JSON data into polished PDF, DOCX, and XLSX reports by mapping your data to Carbone templates and managing the render lifecycle.

Try Carbone in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Carbone integration

    • Describe the outcome and Ceven picks the right Carbone calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Carbone data, across all 11 of its actions.
  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Carbone access.
    • Per user and per environment credentials instead of shared keys.
  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Carbone, when, and on whose behalf.
    • The agent pauses and asks when Carbone is unclear instead of plowing ahead.
  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Carbone.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Carbone action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Carbone, and when to use it.

Generate Carbone Report
Use this when you need to render a final document in PDF, DOCX, or XLSX format by passing a template ID and a JSON data object.
Upload a template
Upload a new template file to the Carbone server to define the layout and data markers for future reports.
Generate Template ID
Create a unique identifier for a new template before you perform the upload process.
Download Template
Pull the original template file from the server using its template ID for review or manual editing.
Delete Carbone Template
Remove a template from the server. Use this only after you have verified the template ID is no longer needed.
Get Carbone Server Status
Check the health and operational status of the Carbone server before triggering a large batch of report renders.
Set Carbone API Version
Specify the API version for subsequent requests to ensure compatibility with your current template logic.

7 actions · scroll to see them all

Frequently asked questions

Ceven acts as the data orchestrator that gathers information from your connected SaaS tools and structures it into a JSON object that matches your Carbone template variables. When you trigger a report, the agent pulls the necessary fields, such as customer name or order total, and maps them to the corresponding tags in your template. This eliminates the need for you to write custom code to format the data. The agent ensures that dates and currencies are passed in the format Carbone expects so the final PDF or DOCX looks professional and requires no manual cleanup after the render is complete.
Yes. Because Ceven uses the template ID to trigger renders, you can upload a new version of your template to the same ID via the Upload a template action. The agent will simply use the latest version of the file stored on the Carbone server for all future requests. This allows you to update your branding, change legal language, or adjust the layout in your local editor and push the update to the server without needing to modify any of the logic inside your Ceven workflow or changing the API calls.
The integration supports all formats provided by the Carbone engine, which primarily includes PDF, DOCX, XLSX, and ODT. You specify the desired output format within the Generate Carbone Report action. For example, if you are generating a financial statement, you can choose XLSX for a spreadsheet output, or for a formal contract, you can choose PDF to ensure the document is read only and maintains its layout across all devices. The agent handles the request and can then pass that resulting file to other tools like Google Drive or Slack.
Yes. Carbone uses specific API versions to maintain stability across different rendering engines. A common quirk is that certain advanced template features only work when a specific API version is active. Ceven provides a Set Carbone API Version action specifically to handle this. If you notice that your complex tables or conditional logic are not rendering correctly, you may need to use this action to align the API version with the version of the template you created. Failing to set the correct version can result in unexpected formatting errors or missing data in the final report.
For users running high volume batch reports, Ceven can use the Get Carbone Server Status action as a pre flight check. The agent calls this endpoint to verify the server is healthy and responsive before pushing a large queue of JSON payloads for rendering. If the server returns a status indicating it is overloaded or down, the agent can be configured to pause the workflow or alert an administrator instead of failing the entire batch. This ensures that your document generation pipeline remains resilient even during peak usage periods.
Carbone is designed as a rendering engine rather than a storage platform. When Ceven sends a JSON payload to generate a report, the data is used to populate the template and create the file. Once the render is complete and the file is delivered, the temporary data used for that specific render is typically purged according to Carbone's data retention policies. Your templates are stored on the server, but the actual customer data passed during a render call is transient. You can always verify the specific data handling and privacy settings within your Carbone account dashboard.
Ceven helps you manage the template lifecycle by automating the creation and deletion process. Instead of manually logging into the Carbone dashboard to create IDs, the agent uses the Generate Template ID action to keep a record of which ID corresponds to which business process in your workflow. If a process becomes obsolete, the agent can use the Delete Carbone Template action to keep your server clean. This programmatic approach ensures that your template library stays organized and that you are not paying for storage of unused assets on your account.
Carbone handles missing data based on the template configuration, usually leaving the tag blank or using a default value if one is defined. Ceven can mitigate this by performing a data validation step before calling the render action. The agent can check if critical fields are present in the source data and, if they are missing, it can either fetch the data from another tool or notify you that the report cannot be generated. This prevents the creation of incomplete documents that would otherwise require manual correction after the PDF has already been generated.

Alternatives to Carbone

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

DocuSign logoDocuSignPandaDoc logoPandaDocAdobe Acrobat logoAdobe Acrobat

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Carbone and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free