Log in Sign up
First-party app
PDFMonkey

PDFMonkey

Generate PDFs and images from PDFMonkey templates.

stable Documents & FilesDeveloper Tools

About

PDFMonkey ships in the w6w first-party pack. It declares 13 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.

App id
io.w6w.pdfmonkey
Version
0.1.0
Author
w6w
Licence
MIT
Categories
Documents & Files · Developer Tools

Overview

PDFMonkey turns a template designed in its Dashboard or visual Builder into PDFs (or images) generated on demand from JSON data, and this app is the generation half of that loop: create a document from a template and payload, poll or wait synchronously for the rendered file, then fetch, list, update or delete it. Beyond generation, it can look up templates and their published/draft settings, and list the PDF engines an account can render with, so a workflow can confirm a template still exists or pick an engine without opening the dashboard.

Generation is asynchronous by default (create, then poll or use a webhook), with a synchronous convenience endpoint that waits up to 6 minutes in a single request for low-volume or interactive use. Every generated document is available as a lightweight DocumentCard (recommended for status/download checks) or a full Document (adds payload and generation logs) — this app exposes both so a workflow only pays for the heavier read when it actually needs the payload back.

Build with PDFMonkey

Three routes to the same 13 actions. The Workflow tab is generated from PDFMonkey's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.

Create Document

create-document

Create a document from a template, optionally queuing generation.

Create Document (Synchronous)

create-document-sync

Create a document and wait for generation to complete (up to 6 minutes).

Create Template

create-template

Create a template. Most users should design templates in the Dashboard instead.

Delete Document

delete-document

Permanently delete a document and its generated file.

Delete Template

delete-template

Permanently delete a template. Linked documents lose their template reference.

Get Document

get-document

Fetch the full document, including payload and generation logs.

Get Document Card

get-document-card

Fetch a document's status and download URL (lightweight — no payload).

Get Template

get-template

Fetch a template's HTML, styles, settings, and PDF engine.

List Documents

list-documents

List generated documents, optionally filtered by template, status, or workspace.

List PDF Engines

list-engines

List the PDF engines available for template generation.

List Templates

list-templates

List template cards for a workspace.

Update Document

update-document

Update a document's payload/meta/template, or trigger generation.

Update Template

update-template

Update a template's content, styles, settings, or engine.

A workflow step names the app and the action, and the editor fills in the connection when you pick one. This is the Step shape from the workflow spec, carrying PDFMonkey's real ids. 

{
  "manifestVersion": "2",
  "name": "pdfmonkey-example",
  "steps": [
    {
      "id": "create-document",
      "uses": {
        "app": "io.w6w.pdfmonkey",
        "action": "create-document",
        "connection": "conn_YOUR_CONNECTION_ID"
      },
      "with": {
        "documentTemplateId": "<documentTemplateId>"
      }
    }
  ]
}

Here are some of the things you can do

  • Create Document

    perform
    create-document

  • Create Document (Synchronous)

    perform
    create-document-sync

  • Create Template

    perform
    create-template

  • Get Document

    read
    get-document

  • Get Document Card

    read
    get-document-card

+8 more actions available

Every app-specific value here is a blank you have to fill in. An app action is reached through the connection that authenticates it, so the address is a connection id, not the app id — and connections belong to your account, so a public page cannot know yours. Create one for PDFMonkey, then fill in the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the parameters that action declares. The call itself is real — the shape is transcribed from the studio's own snippet builder, which prints the same kind of blanks — but nothing in it is specific to PDFMonkey. The Workflow tab is where this app's real ids are.

Install 
npm install @w6w/sdk
yarn add @w6w/sdk
pnpm add @w6w/sdk
deno add npm:@w6w/sdk
Code 
import { W6wClient, isActionRun } from "@w6w/sdk";

// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();

const envelope = await client.run({
  urn: "conn_YOUR_CONNECTION_ID",
  action: "create-document",
  payload: {
    documentTemplateId: "<value>",
    // payload: "<value>",
    // meta: "<value>",
    // status: "<value>",
  },
});

if (isActionRun(envelope)) console.log(envelope.value);
Install the CLI 
npm install -g @w6w/cli
CLI 
w6w run conn_YOUR_CONNECTION_ID --action create-document --payload '{"documentTemplateId":"<value>"}'

Give an AI agent PDFMonkey — without giving it PDFMonkey's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.

One tool call 
{
  "name": "w6w_invoke",
  "arguments": {
    "ref": "app:io.w6w.pdfmonkey#create-document",
    "input": {
      "documentTemplateId": "<documentTemplateId>"
    }
  }
}

Every tool names its target with a single ref. The app: form above doesn't name a connection at all — the host resolves which of the caller's PDFMonkey connections to sign with, and refuses rather than guesses when the answer is ambiguous.

What the agent gets

Credentials it can't read

The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.

A tool surface scoped to the caller

Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.

A durable workflow in one call

Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.

Health-aware discovery

PDFMonkey's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.

The MCP surface is part of the hosted platform. PDFMonkey itself is MIT, and the runtime that executes it is source-available (FSL).

Request MCP access

Health checks

PDFMonkey declares its own checks, so its health is a property of the app rather than something the host guesses at.

service

PDFMonkey platform status

status.pdfmonkey.io is real (updown.io-powered) but publishes no RSS/Atom feed or JSON API at any conventional path.

quota

Documents-per-month headroom

Not safely exposed: the only field (available_documents, on GET /current_user) shares a response with a field that may echo the caller's own API key.