Convert files, HTML, and Markdown into PDF documents through the FileToPDF.dev API.
Convert a file at a public HTTPS URL to PDF, consuming one conversion credit and returning a downloadable PDF. The URL path must end with a supported file extension. Check GET_ACCOUNT_STATUS for remaining credits.
Render an HTML string as a PDF, consuming one conversion credit and returning a downloadable PDF. Check GET_ACCOUNT_STATUS for remaining credits.
Render a GitHub-Flavored Markdown string as a PDF. A successful conversion consumes one conversion credit and returns a downloadable PDF. Check GET_ACCOUNT_STATUS for remaining credits.
Return the connected FileToPDF workspace plan, subscription status, and remaining conversion credits without consuming a credit.
The FileToPDF.dev integration connects your Dench AI CRM directly to FileToPDF.dev, so agents can read and act on your FileToPDF.dev data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
4 actions are available for agents to invoke on your behalf. Every call runs through FileToPDF.dev's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find FileToPDF.dev and click Connect — you'll authorize access through FileToPDF.dev's own sign-in flow. No API keys or code required.
Ask an agent to use FileToPDF.dev in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench FileToPDF.dev integration connects your AI CRM to FileToPDF.dev, so AI agents can work with your FileToPDF.dev data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The FileToPDF.dev integration currently exposes 4 actions, including Convert File URL to PDF, Convert HTML to PDF, Convert Markdown to PDF, and Get Account Status. Agents invoke them on your behalf from chat or from automations.
No. You connect FileToPDF.dev from your Dench workspace using FileToPDF.dev's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through FileToPDF.dev's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the FileToPDF.dev connection from your workspace settings at any time.