Tutorials
Practical, real-world guides for developers — essential workflows broken down into clear steps, with ready-to-use code you can drop into your project.
Build a Morning Briefing Agent for Your Documents
A digest lists what happened; a briefing arrives with the thinking done. One standing prompt over the MCP-connected workspace and Claude sweeps every document's sessions on a headless cron — call-first with evidence and a suggested opener, the next tier in one line each, and the silence flagged.
4 min read
Handle Document Webhooks Reliably
Webhook demos end at 200 OK; production starts there. One plain-JDK Java file covers the three duties the delivery contract implies — ack fast (10s timeout, no retries), dedupe durably (state that survives restarts), and reconcile against the execution log, which carries every failed delivery's full payload for safe replay.
5 min read
See If Clients Actually Read Your Monthly Reports
The report nobody reads is the retainer nobody renews. Tracked links per client sort the portfolio in one sweep — both Meridian stakeholders read cover to cover, Brightpath flicked for 15 seconds, Okafor never opened — and per-page data tells you whether your decision request was ever seen.
4 min read
Build a PDF Engagement Dashboard for Your App
Our dashboard answers our questions; your product has its own. One Node.js script and three endpoints render an activity-first dashboard — documents ranked by reading, KPIs per card, latest readers named — ready to cron onto a wall monitor or fold into your backend. Token stays server-side, always.
4 min read
Mint PDF Tracking Links from ChatGPT
The share decision happens mid-conversation, not in a dashboard tab. The MCP server speaks to any client — including ChatGPT — so 'share the pricing guide with Elif' mints her tracked link inside the draft you were writing, and the same chat checks who read and kills a leaver's old link.
3 min read
Add Per-Recipient Watermarks, Then Track Every Read
Watermarks deter what tracking can only observe — so one pipeline does both: each recipient's copy is stamped with their own name, uploaded as its own tracked document, and shared through their own link. Four chained API calls per name, result URLs flowing straight into tracking, no downloads between.
4 min read
Review the Whole Reading History Before the Sales Call
The sharpest pre-call artifact isn't in the CRM — it's how the prospect read your proposal this week. Pull every session in one call, zoom into the two visits that matter, and write the three-line brief: full read at 07:17, back twenty minutes later for the pricing page. Today's call is the number.
4 min read
Track Who Reads Your Press Kit
Twenty pitches, twenty attached kits, and a silence that could mean anything. Per-journalist links end the blindness: the full read plus asset download says she's writing, the fact-sheet return visit says offer the interview now, and the never-opened rows say re-pitch — not follow up.
4 min read
Let an Agent Draft Follow-Ups From PDF Reading Sessions
'Just checking in' exists because the sender has no information. The reading session is the missing brief: the agent pulls it over MCP — 85 seconds on the Investment page, next steps never reached — and drafts an email that answers what the reader weighed, phrased so the tracking never shows.
4 min read