Share AI-made reports as private, trackable links
Your AI wrote the report. Publish it as a clean web page on your own domain, put it behind a password, and see how often it gets opened.
https://mcp.cloud71.host/mcpyou › Publish this report to cloud71 and give me the link.
Claude › calling deploy_files…
✓ live at https://q3-report.cloud71.site
AI tools now turn out finished deliverables: research briefs, client reports, audits, data summaries with charts. Pasting that into an email flattens the layout, and attaching an HTML file asks the reader to download something and trust it. A hosted link opens in any browser and looks the way it was designed — on a laptop or a phone.
With the cloud71 connector, you ask Claude or ChatGPT to publish the report and the link comes back in the same chat. Then add what a client-facing report needs: a password, your own domain, an opt-in email form, and analytics that show visits and referrers. When the numbers change, ask your AI to update the report and the same link shows the new version.
Try saying
- “Publish this report to cloud71 and give me the link.”
- “Update my ‘q3-report’ site with the new numbers and republish.”
- “Set the custom domain reports.acme.com on my ‘q3-report’ site.”
- 1
Have your AI write it
Ask for a single, self-contained HTML page for the cleanest result. A PDF works too.
- 2
Ask it to publish
Say “Publish this report to cloud71 and give me the link.” No agent handy? Drop the file into cloud71.
- 3
Lock it, then share
Turn on a password and add your domain in the dashboard, send the link, and watch the visits.
Everything the link needs
Password protection
Keep client work private. Readers enter a password before the report loads (Starter, $5/mo).
On your own domain
reports.yourfirm.com reads as yours, not a file host's (Starter, $5/mo).
Know it was opened
Visits and top referrers for every report — no tracking code to add.
Update in place
Republish revised numbers to the same link. The last 5 versions are kept.
Links that expire
Publishing from an automation? Set an expiry on the API call and the link expires after it.
Capture leads
Add an opt-in email form to a public report and collect readers' emails (Starter, $5/mo).
Common questions
Ask the AI that wrote it to publish it through the cloud71 connector, or save it as an HTML or PDF file and drop it into cloud71. Either way you get a link that opens in any browser.
Publish the report, then turn on password protection for that site (Starter and up). Visitors see a password prompt before anything loads. Automations can set the password in the same API call with the x-c71-password header.
cloud71 shows how many visits a report gets and where they came from, not who each visitor is. If you need names, turn on lead capture to collect emails from readers who opt in.
Either works. HTML gives you a responsive page with working links and charts; a PDF is shown in a built-in viewer. For the cleanest result, ask your AI for one self-contained HTML file.
Yes, through the API: send x-c71-ttl with a number of seconds or an ISO date when you publish, and the link expires after that time. Expired sites are removed by a scheduled sweep, so treat the expiry as approximate rather than to-the-minute.
Publishing a report is free on the free plan (one site, updated as often as you like). Password protection, lead capture, and custom domains start on Starter at $5/mo; Pro ($19/mo) gives unlimited sites for agents that publish all day.
Yes. Point it at a named site and each run updates the same link, or create a new site per report on a plan with room for more sites. Scheduled jobs can call the REST API directly.