Use Pdfless from Claude
Add the Pdfless connection to a Space that runs Claude, then use it from every channel in that Space.
Connect Pdfless once, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.
Add the Pdfless connection to a Space that runs Claude, then use it from every channel in that Space.
Add the Pdfless connection to a Space that runs Codex, then use it from every channel in that Space.
Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.
Pdfless turns HTML and CSS templates into PDF documents through a hosted API, built for invoices, reports, and labels. In type.com, an operations team can ask Claude to confirm the workspace is active or list the document templates available before generating a new batch of files.
Connect Pdfless once, then decide which Spaces can use it in threads, skills, automations, and coding work.
Once Pdfless is connected in type.com, install the type.com CLI, and Claude Code or Codex can call its tools with type-cli integrations call. Calls run with your type.com access, and the credentials stay on type.com's servers.
In a Space with Pdfless connected, describe the job, and type.com proposes an automation with its trigger, schedule, and destination. Runs can start on a schedule or from a webhook, Slack, GitHub, Linear, email, or RSS, and each run leaves a thread the team can read.
Check the workspace's active status and basic details before kicking off a batch of document generation requests.
Get our Pdfless workspace status before I start generating this week's invoices.
List document templates in the workspace to confirm the one you need already exists before referencing it elsewhere.
List our Pdfless document templates so I can find the shipping label template.
Page through all document templates to see what's been set up, useful before cleaning up unused ones.
List all templates in our Pdfless workspace and flag any that look unused.
Returns the workspace's name, creation date, and whether it's currently active.
Lists document templates set up in the workspace, with pagination support.
Pdfless is a document-generation API for producing PDFs from templates and data. Integrations can create templates, authenticate HTTP API calls, generate PDFs programmatically, use SDKs, handle API errors, and automate invoices, reports, labels, or other HTML/CSS-driven documents.
Yes. With a Pdfless connection shared to a type.com Space, Claude can confirm the workspace is active and list document templates, all from a thread.
Pdfless uses an API key, added once by an admin when the connection is created. Spaces generating documents can use it without seeing the key.
Yes. A recurring check, such as confirming the workspace is active before a daily batch run, can be set up as a type.com automation.
Yes. Once Pdfless is connected in type.com, install the type.com CLI, and Claude Code or Codex can call its tools with type-cli integrations call. Calls run with your type.com access, and the credentials stay on type.com's servers.
Yes. In a Space with Pdfless connected, describe the job, and type.com proposes an automation with its trigger, schedule, and destination. Runs can start on a schedule or from a webhook, Slack, GitHub, Linear, email, or RSS, and each run leaves a thread the team can read.
Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.
Connect Tally to Claude in type.com to create forms from a description, review form details, delete old forms, and manage webhooks for submissions.
Connect Typeform to Claude in type.com to create forms with logic, upload images, set custom themes, add workspaces, and configure webhooks.
Connect Typless to Claude in type.com to check document types, review your profile, and keep account details current from a thread.
Connect KnoCommerce to Claude in type.com to pull post-purchase survey responses, benchmark questions, and manage webhooks in a thread.