PDFMonkey
Also an agent toolPDFMonkey document-generation integration: create/generate PDFs from templates, poll status, manage templates, and react to Svix-signed document.generation webhooks
12 actions · 3 triggers
The PDFMonkey integration lets you connect PDFMonkey to your automations with 12 actions and 3 triggers — and every action is also a tool an AI agent can call. Examples: Get Current User, Generate Document, Get Document, Update Document, Delete Document. No blank-canvas wiring — connect it and use it in your workflows.
Every action below is also a tool an AI agent can call — the same pack powers your workflows and your agents.
Triggers 3
Events in PDFMonkey that can start a workflow.
Document Generation Success
Fires when a PDFMonkey document finishes generating successfully (document.status == 'success'); download_url is available. Delivered via Svix, verified with the registered svix signature handler.
Document Generation Failure
Fires when a PDFMonkey document fails to generate (document.status == 'failure'); failure_cause describes the error. Delivered via Svix, verified with the registered svix signature handler.
New / updated PDFMonkey document
Fires for documents updated since the last poll; filter q[status]=success for completed PDFs.
Actions 12
What Zervanor can do in PDFMonkey.
Document Templates4
Get Template
Fetch the full DocumentTemplate including body, scss_style, settings and sample_data (GET /document_templates/{id}).
Create Template
Create a document template programmatically (POST /document_templates). Body wrapped under 'document_template'.
Update Template
Update an existing template; only included fields change (PUT /document_templates/{id}). Body wrapped under 'document_template'.
Delete Template
Permanently delete a template (DELETE /document_templates/{id}). Returns 204 No Content.
Documents4
Generate Document
Create a document and (with status 'pending') queue asynchronous generation (POST /documents). Body is wrapped under the 'document' key. Returns 201 with { document: { id, status, ... } }. WRITE test target (paired with delete_document cleanup).
Get Document
Fetch the full Document including payload, generation_logs and checksum (GET /documents/{id}). Poll until status is success/failure, then read download_url.
Update Document
Update a draft document; set status 'pending' to trigger generation (PUT /documents/{id}). Body wrapped under 'document'; only included fields change.
Delete Document
Permanently delete a document and its stored file (DELETE /documents/{id}). Returns 204 No Content. CLEANUP test target.
Document Cards2
Get Document Card
Fetch the lightweight DocumentCard for an id (GET /document_cards/{id}) — no payload/generation_logs/checksum. Recommended for status polling.
List Document Cards
Paginated list of lightweight document cards, max 24/page (GET /document_cards). Filterable by template, status, workspace, updated-since cursor and search. Polling-trigger candidate.
Current User1
Get Current User
Return the authenticated PDFMonkey account (GET /current_user). PDFMonkey's documented way to verify an API key; parameterless, safe, read-only. READ test target.
Document Template Cards1
List Template Cards
Paginated list of lightweight template cards (GET /document_template_cards). Requires a workspace filter; optionally filter by folders, sort and page.
Nothing matches your search.
Automations using PDFMonkey
Build your own automation with PDFMonkey in the visual builder.
Frequently asked questions
What can I automate with PDFMonkey?
12 actions are available — for example: Get Current User, Generate Document, Get Document, Update Document, Delete Document, and more.
Which PDFMonkey events can start a workflow?
3 triggers — for example: Document Generation Success, Document Generation Failure, New / updated PDFMonkey document.
Can PDFMonkey be used as an AI agent tool?
Yes. Every PDFMonkey action automatically becomes a tool an AI agent can call — the same pack powers both your workflows and your agents.
How is the PDFMonkey integration modelled?
PDFMonkey is modelled as a versioned connector pack, and the steps that need reasoning fall to first-party agents hosted in the same runtime as the workflows.