Apple Shortcuts

The Sitepaste API works from anything that can make an HTTP request, including the Shortcuts app on iPhone and Mac. That makes it possible to write a post in Apple Notes and publish it without opening a browser.

Publishing this way requires an API token, which is a Pro plan feature. Create one in the dashboard under Account > Tokens. A shortcut that only writes pages needs the content scope. One that also deploys needs deploy as well, because deploying is its own request to /sites/{siteId}/deployments.

Apple Notes shortcuts

Sitepaste maintains step-by-step instructions for two shortcuts in the integrations repository:

  • Publish Note to Sitepaste: pick a recent note, choose blog, docs, or standalone, and publish it. Running it again on the same note updates the existing page.
  • Publish Folder to Sitepaste: publish every note in a Notes folder with one content type, the way the GitHub Action publishes a directory.

A few things to know about Notes as a writing surface:

  • Shortcuts extracts note content as plain text, so rich-text formatting is lost. Write Markdown syntax directly in your notes and it renders properly on your site.
  • Images embedded in notes cannot be extracted by Shortcuts. Upload them through the dashboard or the media API and reference them by URL.

Roll your own shortcut

If you do not use Apple Notes, the recipe is one “Get Contents of URL” action:

  1. URL: https://sitepaste.com/api/v1/public/sites/default/pages, method POST.
  2. Header Authorization with value Bearer sp_your_token_here.
  3. A JSON request body holding title and content, filled from “Ask for Input” actions.

What the action sends is just the page:

{ "title": "My post", "content": "Hello" }

The slug is generated from the title, and the page is created as a blog post unless you add a contentType field. The reply is a 201 whose Location header names the page, so a shortcut can show you where it landed. Running it a second time on the same title answers 409 rather than replacing the page.

That publishes the page but does not deploy it. Add a second “Get Contents of URL” action posting to https://sitepaste.com/api/v1/public/sites/default/deployments with the same header and no body. Your site rebuilds.

To make a re-run update the page rather than fail on a slug it already used, send the batch instead. Its entries upsert by slug, so the same shortcut run twice edits the page rather than colliding with it. Point the first action at .../pages/batch and give it this body:

{ "pages": [{ "title": "My post", "content": "Hello" }] }

One request is fewer moving parts on a phone; two lets you write several posts and deploy once. Either way the deploy needs the deploy scope.

Keep the deploy action after it either way. That’s enough for quick posts, link posts with commentary, or notes you want on your site the moment you think of them. The request can also set sections, drafts, tags, and a target site. See the POST /sites/{siteId}/pages reference for everything it can do.

Built with Sitepaste