How do I use Shortcuty's version checking system in my shortcut?

Shortcuty's version checking system allows your shortcuts to automatically detect when newer versions are available and prompt users to update. This guide covers both the automatic shortcut updater tool and manual implementation methods.

Shortcut Updater Tool (Automatic)

The easiest way to add version checking to your shortcuts - no manual coding required.

What is the Shortcut Updater Tool?

The Shortcut Updater Tool is a feature in the Shortcuty iOS app that automatically adds update-checking code to your shortcuts. It downloads your shortcut from iCloud, injects the updater mechanism, and returns a ready-to-use shortcut file.

How to Access:

  • iOS App: Open the Shortcuty iOS app → Navigate to "My Shortcuts" → Select a shortcut you've uploaded → Tap "Developer Tools" → Select "Auto-Updater Tool"
  • Web Version: Go to "My Shortcuts" on the website → Click "Developer Tools" on a shortcut → Select "Auto-Updater Tool"

Note: The Auto-Updater Tool is available in Developer Tools on both the iOS app and web version for shortcuts you've uploaded.

How It Works:

  1. The tool downloads your shortcut from iCloud using the sharing URL
  2. It automatically injects the appropriate update-checking mechanism
  3. You receive a processed shortcut file ready to install
  4. Replace your original shortcut with the processed version

Template Options:

  • API Template: Uses native URLs (Get Contents of URL) - works on any device without the Shortcuty app installed
  • Action Template: Uses the "Check Shortcut Update" action - requires Shortcuty app installed on user devices

Benefits:

  • No manual coding required
  • Handles version comparison logic automatically
  • Supports semantic versioning (1.2.3)
  • Works with both native URLs and Shortcuty actions

Manual Implementation Methods

If you prefer to implement version checking manually, here are two methods you can use.

Method 1: Using Check Shortcut Update Action

This method uses Shortcuty's built-in action for update checking. It requires the Shortcuty app to be installed on user devices.

Implementation Steps:

  1. Add the "Check Shortcut Update" action to your shortcut
  2. Provide your shortcut's UUID (found in "My Shortcuts" in the Shortcuty app)
  3. Provide the current version number of your shortcut
  4. Add an "If" statement after the check
  5. If the result is true (update available):
    • Add "Open App" action → Select "Shortcuty"
    • Add "Stop Shortcut" action

Requirements:

  • Shortcuty app must be installed on user devices
  • Shortcut must have a UUID (obtained after submitting to Shortcuty)

Benefits:

  • Simplest manual implementation
  • Automatic version comparison
  • App automatically shows update screen when update is available

View Check Shortcut Update action documentation →

Method 2: Using Native URLs

This method uses standard Shortcuts actions and works on any device, even without the Shortcuty app installed.

Get Your URLs:

  • Open "My Shortcuts" in the Shortcuty iOS app
  • Select your shortcut
  • Find the "Version" URL and "Download Link" URL
  • Copy these URLs for use in your shortcut

Implementation Steps:

  1. Add "Get Contents of URL" action
  2. Set the URL to your version endpoint (returns current version as plain text)
  3. Store the result as "Latest Version"
  4. Add "If" statement
  5. Condition: Latest Version > Current Version
  6. If true:
    • Add "Open URL" action
    • Set URL to your download link endpoint
    • Add "Stop Shortcut" action

Requirements:

  • Shortcut must have a UUID (obtained after submitting to Shortcuty)
  • No additional apps required

Benefits:

  • Works on any device without Shortcuty app
  • Uses only native Shortcuts actions
  • Full control over update flow

How Version Checking Works

Understanding the technical details of Shortcuty's version checking system.

Semantic Versioning

Shortcuty supports semantic versioning (e.g., 1.2.3) for version comparison. The system compares versions numerically, so 1.2.3 is considered newer than 1.2.2, and 2.0.0 is newer than 1.9.9.

Version Comparison Logic

The system compares version strings by splitting them into components and comparing each part numerically. This ensures accurate version ordering regardless of string length.

Update Notifications and Tracking

When shortcuts check for updates using Shortcuty's version checking API:

  • Version checks are automatically tracked for analytics
  • Developers can see version check statistics in their analytics dashboard
  • This helps estimate active users of your shortcuts
  • Anonymous usage statistics are collected server-side

Analytics Integration

Version checks contribute to your shortcut's analytics:

  • Track how many users are actively using your shortcuts
  • Monitor update adoption rates
  • Identify which versions are still in use
  • View version check trends over time

Best Practices

  • Always use semantic versioning (major.minor.patch format)
  • Place update checks at the beginning of your shortcut
  • Use "Stop Shortcut" after opening the update URL to allow installation
  • Test update checks with different version numbers before releasing
  • Keep your shortcut's UUID and version number easily accessible for updates

Changelog API Endpoint

Retrieve changelog history for shortcuts using the changelog API endpoint.

GET
/api/shortcuts/{identifier}/changelog
Public

Returns the approved changelog history for a shortcut.

Path Parameters

  • identifier - The shortcut UUID or ID

Query Parameters

None

Authentication

Public endpoint (no authentication required)

Example Request

https://shortcuty.app/api/shortcuts/00000000-0000-0000-0000-000000000000/changelog

Response (200 OK)

JSON object containing shortcut name and changelog entries:

{
  "shortcut_name": "My Shortcut Name",
  "changelog": [
    {
      "version": "1.2.0",
      "changelog": "Fixed critical bug in data processing",
      "date": "2024-01-15T10:30:00Z"
    },
    {
      "version": "1.1.0",
      "changelog": "Added new feature for better performance",
      "date": "2024-01-10T08:15:00Z"
    }
  ]
}

Response Fields

Root Object:

  • shortcut_name (string) - Name of the shortcut
  • changelog (array) - Array of changelog entries, ordered by date (newest first)

Changelog Entry Object:

  • version (string) - Version number for this update
  • changelog (string) - Changelog text describing the update
  • date (string) - ISO 8601 formatted datetime (UTC) when the update was approved

Error Responses

404 Not Found

{
  "error": "Shortcut not found"
}

Returned when the shortcut doesn't exist.

Notes

  • Only returns approved changelog entries
  • Entries are sorted by approval date (newest first)

Use Case

Display changelog history for shortcuts, showing users what has changed in each version. Perfect for displaying update history in your shortcuts or on external websites.

Related Resources

Additional documentation and resources for version checking and shortcut development.

Documentation Links