Skip to content
pagesendpagesend
Open navigation
ChatGPT guide

Give finished work a page you can share.

Use a supported ChatGPT connection to publish static content to pagesend, with explicit workspace and audience choices.

Start with the connection instructions

Open Agents, choose ChatGPT, and follow this deployment’s setup instructions. The Markdown connection guide includes the configured MCP address and troubleshooting steps. Your client needs to reach that HTTPS server; a local loopback address is not reachable from ChatGPT on the web.

Connection availability depends on the ChatGPT surface and workspace settings. Use the supported OAuth flow, then sign in with pagesend, choose the intended workspace, and review access. Never paste account cookies or access tokens into the conversation.

Return to ChatGPT and confirm that a read-only pagesend call succeeds. A package or configured server address does not imply public marketplace listing or compatibility with every client.

Ask for complete static files

Ask for a finished HTML report, guide, or supported static page. Include the content and any local styles or assets needed to display it. Review generated claims and sources before publishing. See sharing AI reports for a practical report checklist.

For multiple files, use a bundle rooted at index.html. A JavaScript app must follow the supported pagesend runtime and routing contract. Keep private credentials and server-only configuration out of the files.

Choose a supported transfer path

Bounded inline HTML can be prepared, transferred, validated, and explicitly published through separate tools. For larger files, the client must have a supported, authorized execution environment with access to the actual bytes and the packaged helper. A generated file path by itself does not transfer a file.

Arbitrary remote download links and provider-file imports are not supported merely because a client returns a URL. If a file cannot be transferred through the supported tools, download the finished output and upload it in the browser. That is a browser-upload workflow, not an entirely in-chat publication.

Review publication and sharing

New pages start private. A ready upload is not yet published, and publishing files does not make them public. Review the preview and intended audience. Public sharing needs separate permission and explicit intent.

Saved-data access is also separate. Publishing or changing the file audience does not authorize an agent to read private viewer records or change collection permissions.

Keep the link for later revisions

Keep the returned page identity and canonical link. Ask for an update to the same page, using its current publication state. If a tool reports a conflict, review the current version before retrying. Report a page as published only after the server acknowledges publication.

Manage or revoke the connection in Agents. For a public page intended for search, choose search visibility independently.