ceven

Cloudlayer

Turns raw HTML and live URLs into professional PDFs and images, then routes those assets to your storage or sends them directly to customers.

Try Cloudlayer in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Cloudlayer integration

    • Describe the outcome and Ceven picks the right Cloudlayer 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 Cloudlayer data, across all 16 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Cloudlayer 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 Cloudlayer, when, and on whose behalf.
    • The agent pauses and asks when Cloudlayer is unclear instead of plowing ahead.

  4. Enterprise grade security

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

Supported tools

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

Convert HTML to PDF
Use this when you have raw HTML content that needs to become a PDF document for a client or internal record.
Convert URL to PDF
Use this to turn a public webpage into a PDF with specific control over margins, paper size, and headers.
HTML to Image
Use this to render base64 encoded HTML into a PNG, JPEG, or WebP image file.
Convert URL to Image
Use this when you need a screenshot of a live webpage using dynamic parameters for viewport size.
Get Asset
Pull the metadata or the direct download URL for a specific asset using its unique ID.
List Assets
Pull a list of the ten most recent assets generated by your account to track recent activity.
Add Storage
Use this to attach a new external bucket or container where Cloudlayer should save generated files.
List Storage Configurations
Pull all active storage settings to verify where your PDFs and images are being routed.
Get API Status
Use this to check if the Cloudlayer API is reachable and responding before starting a bulk job.
Update Asset Metadata
Use this to add tags or descriptions to a generated asset for better organization in your storage.
Delete Asset
Use this to remove a specific asset from the Cloudlayer cache to maintain data privacy.
Create Webhook
Set up a callback URL that notifies your workflow the moment a PDF generation is complete.

12 actions · scroll to see them all

Frequently asked questions

Ceven manages this by utilizing Cloudlayer webhooks. When the agent triggers a PDF conversion, it does not just wait and hope the file appears. Instead, it registers a unique callback URL for that specific request. Cloudlayer processes the HTML or URL in the background and sends a POST request back to Ceven the moment the file is ready. The agent then wakes up, retrieves the final asset URL, and proceeds to the next step in your workflow, such as emailing the document to a client or uploading it to a CRM. This ensures your workflows do not time out during complex renders.
Yes, but the process happens at the Cloudlayer account level. You must upload your custom font files to your Cloudlayer dashboard first. Once the fonts are registered in your account, the agent can reference them within the CSS of the HTML it sends for conversion. If you use a URL for conversion, Cloudlayer will render the page as a browser would, meaning any fonts hosted on that page via @font face will be rendered automatically. The agent simply ensures the HTML structure is clean so the rendering engine can apply your styles without errors.
By default, Cloudlayer stores assets in its own temporary storage, but Ceven encourages using the Add Storage action to connect your own AWS S3, Google Cloud Storage, or Azure Blob storage. When you configure a personal bucket, Cloudlayer pushes the file there immediately upon completion. This is critical for security and long term retention because files stored on Cloudlayer servers are subject to automatic cleanup policies. By routing assets to your own storage, the agent ensures you have permanent ownership of every PDF and image created through your workflows.
Cloudlayer has specific payload limits depending on your subscription tier. For most users, sending massive blocks of base64 encoded HTML can lead to 413 Request Entity Too Large errors if the payload exceeds the API limit. To avoid this, the agent is programmed to prefer URL based conversion for large documents. If you must use raw HTML, the agent will attempt to optimize the content. If you consistently hit these limits, you will need to upgrade your Cloudlayer plan or host the HTML on a private URL that the agent can then pass to the API.
Rendering pages behind a login is complex because the API needs session cookies or authorization headers. The agent can pass custom headers or cookies to Cloudlayer if you provide them in the workflow context. However, for highly secure sites with multi factor authentication, the agent cannot bypass the login screen. The best practice here is to have the agent generate a temporary signed URL for the content or provide the raw HTML directly via the HTML to PDF action, which bypasses the need for the renderer to authenticate with a third party site.
Cloudlayer provides detailed error codes in the API response. If a URL returns a 404 or a 500 error, the agent catches that response immediately. Instead of failing the entire workflow silently, the agent can be configured to retry the request after a short delay or notify you via Slack that the source page is down. You can set specific timeout parameters in the Convert URL to PDF action to tell the agent exactly how long to wait for a page to load before deciding it is a failure and triggering the fallback path.
Absolutely. The agent has full access to the paper size and orientation parameters. You can tell the agent to create a document in A4, Letter, or a completely custom dimension in pixels or inches. You can also specify whether the page should be portrait or landscape. This is handled during the initial request call. For example, if you are generating a wide financial spreadsheet, the agent will automatically set the orientation to landscape and adjust the margins to ensure no data is cut off during the rendering process.
Yes, Cloudlayer uses a headless browser to render content, meaning it executes JavaScript just like Chrome. This allows the agent to capture pages that rely on React, Vue, or other frameworks to display data. You can specify a wait condition, telling the agent to wait for a specific element to appear or for a certain amount of time to pass before the snapshot is taken. This ensures that dynamic charts or loading spinners are fully resolved and the final PDF contains the actual data rather than a loading screen.

Alternatives to Cloudlayer

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

Puppeteer logoPuppeteerBrowserless logoBrowserlessDocRaptor logoDocRaptor

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Cloudlayer 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