← PapelyCONTENT HISTORY

Update to Papely

Snapshot Nov 1, 2026 · 00:10 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Papely and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Create PDF documents from the user's Papely templates. Use when the user asks to list their Papely templates, see the fields of a template, generate one or more PDFs from a template, get a download link, register an image for a template, or email generated PDFs.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: Create PDF documents from the user's Papely templates. Use when the user asks to list their Papely templates, see the fields of a template, generate one or more PDFs from a template, get a download link, register an image for a template, or email generated PDFs.\n---\n\n# Create PDFs with Papely\n\nUse the Papely tools to fill the user's PDF templates with data. Explicit instructions from the user take priority over this guide.\n\n## Workflow\n\n1. Call `list_templates` to find the template the user means. If more than one template could match, ask which one.\n2. Call `get_template` to read its fields and the value each field expects:\n   - `text`, `date` and `qr`: a string.\n   - `image`: an `img_<id>` reference from `register_image_from_url`, or `\"\"`.\n   - `table`: an array of rows. Each row has exactly one string (or `null`) cell per entry of the field's `columns`, in the same order.\n3. Build `data` with the field keys from `get_template`. Use only values the user gave you; do not invent names, codes or other values. Ask for any value you need. A field you leave out renders blank or with its default.\n4. Call `generate_document` for one PDF, or `generate_batch` for up to 100 PDFs from the same template in one job (the batch downloads as a ZIP file). Each document counts toward the generation limit of the workspace. Pass an `idempotencyKey` if you may need to retry the same call.\n5. Call `get_generation_status` every few seconds until the status is `completed` or `failed`. If it failed, tell the user the error message.\n6. When it is completed, call `get_generation_document` and give the user the download link. The link expires after a short time; call the tool again for a new link.\n\n## Images\n\nFor an image field, call `register_image_from_url` with a public HTTPS URL to a PNG or JPEG image. Use the returned `img_<id>` as the value of the field. A registered image can be reused in later generations.\n\n## Email delivery\n\nOnly email documents when the user asks for it. An email cannot be undone, so confirm the recipients with the user before you generate. Put each recipient's address in `data.email` (and optionally their name in `data.name`) and pass the `email` template block. Documents without an email address are generated but not sent. Use `get_generation_emails` to report the delivery status of each recipient.\n\n## When not to use Papely\n\nDo not use these tools to read, summarize or convert existing files, or to write free-form text. Papely only creates PDFs from the templates in the user's workspace; templates are created and edited in the Papely web app.\n"
}

SHA-256 of public snapshot: b02e56dbc3a45293c971542afc57c8681399a457155cb2bdba2a194d3c67517f