CloudPDF

@CloudPDF show me our account usage and remaining document allowances for this billing period

Your CloudPDF organization is on the Professional plan. This month you've uploaded 847 of 5,000 allowed documents, consumed 12.3 GB of 50 GB storage, and logged 18,420 document views. You have 4,153 documents remaining in your monthly quota and 37.7 GB of storage available. Your plan renews on the 15th.

This example demonstrates the read-only account inspection capability. Useful for capacity planning before bulk uploads. Requires a valid API key with account-read scope; CloudPDF does not expose per-user breakdowns, only organization-level totals.

@CloudPDF delete document uuid:a7f3c891-4d2e-4b89-9c1a-5e8f6d2b3a4c because we uploaded the wrong contract version

Document a7f3c891-4d2e-4b89-9c1a-5e8f6d2b3a4c has been permanently deleted from CloudPDF. This action is irreversible—CloudPDF provides no trash or recovery mechanism. Any public or private links to this document will now return 404 errors. If webhook subscriptions were monitoring this document, they will no longer fire events for it.

Showcases the destructive delete operation. Use with caution: CloudPDF deletions are immediate and permanent, with no undo path. Confirm the UUID before running this prompt. Requires API key with document-delete permissions, which many organizations restrict to admin roles.

@CloudPDF create a webhook that posts to our Slack channel whenever someone views the Q1-financials.pdf document so we can track investor interest

I've created webhook subscription ID 8472 in your CloudPDF account. It will POST to your specified Slack endpoint whenever document Q1-financials.pdf (uuid: b3e9f2a1-7c4d-4a8e-9f1b-6d3e5a7c2b9f) receives a view event. CloudPDF will include viewer metadata (IP, timestamp, duration) in the payload. Note that high-traffic documents may trigger rate limits on your Slack webhook—consider batching or filtering if views exceed 100/hour.

Illustrates webhook creation for event-driven workflows. CloudPDF supports document, collection, tracker, lead, and file-processing events. You must provide a valid HTTPS endpoint and ensure your API key has webhook-write scope. Webhook payloads arrive in real-time but offer no built-in retry logic if your endpoint is down.

When CloudPDF makes sense for proposal follow-up at 5-rep scale

A five-person sales team sends custom proposals through CloudPDF and wants to know which prospects opened the deck and how long they spent on pricing pages. The webhook tools let you pipe open and view events into Slack or your CRM without writing code. This works cleanly if your team sends fewer than 200 proposals a month and you're already paying for CloudPDF's tracker tier. The trade-off: CloudPDF charges per tracked document, so if you're trialing with free-tier limits or sending high-volume collateral, the webhook quota runs out fast. If your use-case is pure storage and you don't need view analytics, a simpler MCP like Google Drive or Dropbox is cheaper and easier to audit.

CloudPDF for quarterly compliance sweeps in professional services

A 12-person consulting firm stores signed SOWs in CloudPDF and needs to pull metadata—upload date, permissions, processing status—during quarterly audits. The Get Document and Get Account tools let you script a compliance report that checks whether every contract is indexed, who can view it, and whether storage is approaching plan limits. This scenario wins if your firm already uses CloudPDF as the system of record and you need programmatic access without opening the web UI 80 times. The boundary: if you're storing contracts across multiple platforms (Google Drive, SharePoint, CloudPDF), unifying the audit through one MCP creates more friction than it solves. Switchy's value here is the scripted pull, not the storage consolidation.

When CloudPDF webhooks streamline new-hire handbook distribution

A 20-person startup sends onboarding handbooks through CloudPDF and wants to confirm each new hire opened the benefits PDF before their first day. The Create Webhook tool lets HR subscribe to document-open events and log them in Notion or trigger a Slack reminder if the handbook sits unread for 48 hours. This works if your onboarding cadence is predictable—say, two hires a month—and you want lightweight automation without building a custom integration. The limit: CloudPDF's webhook model charges per event, so if you're scaling to 10+ hires a month or sending multi-document packets, the per-event cost and webhook management overhead outpace a simpler email-receipt workflow. If tracking is nice-to-have, not compliance-critical, skip the MCP and use read receipts.