A searchable reference for every app URL scheme — 53 entries covering productivity, dev, and communication tools. Use this to look up the exact deep-link format an app expects, or to confirm whether a scheme exists at all.
50 of 53 schemes can be wrapped into a universal HTTPS link via Shortlink.
| App | Scheme | Wraps? |
|---|---|---|
| Slack | slack:// | Yes |
| Obsidian | obsidian:// | Yes |
| Zoom | zoommtg:// | Yes |
| Notion | notion:// | Yes |
| Figma | figma:// | Yes |
| Linear | linear:// | Yes |
| VS Code | vscode:// | Yes |
| Cursor | cursor:// | Yes |
| GitHub Desktop | x-github-client:// | Yes |
| Spotify | spotify:// | Yes |
| Apple Music | music:// | Yes |
| 1Password | onepassword:// | Yes |
| Discord | discord:// | Yes |
| Telegram | tg:// | Yes |
| whatsapp:// | Yes | |
| Signal | sgnl:// | Yes |
| Microsoft Teams | msteams:// | Yes |
| Webex | webex:// | Yes |
| Asana | asana:// | Yes |
| Trello | trello:// | Yes |
| Jira | jira:// | Yes |
| Confluence | confluence:// | Yes |
| ClickUp | clickup:// | Yes |
| Monday | monday:// | Yes |
| Airtable | airtable:// | Yes |
| Coda | coda:// | Yes |
| Craft | craftdocs:// | Yes |
| Drafts | drafts:// | Yes |
| Fantastical | fantastical2:// | Yes |
| OmniFocus | omnifocus:// | Yes |
| Things | things:// | Yes |
| Bear | bear:// | Yes |
| DEVONthink | x-devonthink-item:// | Yes |
| Hookmark | hook:// | Yes |
| Logseq | logseq:// | Yes |
| Roam Research | roam:// | Yes |
| Anytype | anytype:// | Yes |
| Tana | tana:// | Yes |
| Capacities | capacities:// | Yes |
| Reflect | reflect:// | Yes |
| Mem | mem:// | Yes |
| Sublime Text | subl:// | Yes |
| JetBrains | jetbrains:// | Yes |
| Warp | warp:// | Yes |
| iTerm | iterm2:// | Yes |
| Tower | gittower:// | Yes |
| Sourcetree | sourcetree:// | Yes |
| YouTube Music | youtubemusic:// | Yes |
| Apple Mail | message:// | Yes |
| Mail (mailto) | mailto: | No |
| Phone | tel: | No |
| SMS | sms: | No |
| FaceTime | facetime:// | Yes |
A URL scheme is the protocol identifier at the start of a URL — the part before the colon. Standard schemes like https, http, mailto, and tel are recognized by every browser and platform.
Custom URL schemes like slack:// or obsidian:// are registered by individual applications. When the operating system sees one of these schemes in a clicked link, it hands the URL to the app that registered it. This is how apps implement deep links into specific channels, vaults, files, or meetings.
On macOS and iOS, apps declare their schemes in Info.plist under CFBundleURLTypes. On Windows the registration lives in the Registry under HKEY_CLASSES_ROOT. On Android, apps declare intent filters in their manifest with a custom scheme.
Once registered, clicking a link with that scheme prompts the OS to launch the app and pass it the full URL. The app then parses the URL’s host, path, and query parameters to decide what to open.
The browser is the messenger; the OS is the dispatcher. When you click a custom-scheme link, the browser doesn’t try to fetch it — it asks the OS which app handles that scheme. The OS launches the app and passes it the URL.
Problems arise when content platforms (Notion, Confluence, Gmail, GitHub) sanitize or strip non-HTTPS links before rendering. Even though the browser would correctly hand off the URL to the OS, these platforms never let the link reach the browser as a clickable element. Wrapping the scheme in an HTTPS link via Shortlink works around this.
Teams across the US East Coast lean heavily on Notion as a central wiki, with Slack as the comms layer. Custom scheme URLs are most often shared inside Notion docs, where they fail silently.
Use case: Wrap your slack:// channel deep links into HTTPS so they survive being pasted into Notion runbooks and onboarding pages.
West Coast product and design teams rely on Figma and Linear daily. Both platforms understand their own deep-link schemes but block competing ones.
Use case: Convert figma:// prototype links into universal URLs you can drop into Linear specs without breaking the click target.
UK teams frequently coordinate across Microsoft Teams, Confluence, and Jira — all of which sanitize non-HTTPS URLs aggressively.
Use case: Embed Zoom and Slack deep links inside Confluence pages and Jira tickets by wrapping the original scheme in a Shortlink.
In German-speaking markets, Confluence and Jira dominate enterprise documentation. Both block custom schemes natively.
Use case: Paste Shortlinks into Confluence pages to give teammates one-click access to Zoom calls or Figma prototypes from your specs.
French product teams often combine Notion with Slack and Figma. Cross-tool linking breaks the moment a custom scheme leaves its native app.
Use case: Generate Shortlinks once and reuse them in Slack, Notion, and email — the same HTTPS link works in every context.
Engineering teams across India frequently ship across time zones, leaning on async tools like Slack, Notion, and GitHub for handoffs.
Use case: Wrap GitHub Desktop and VS Code deep links into Shortlinks so engineers on the next shift can open them directly from a Notion handoff doc.
Tokyo-based teams often pair Slack with Figma and Notion. Sharing prototype links across these tools is common, and equally commonly broken.
Use case: Build figma:// and slack:// deep links once with the Shortlink builder, then reuse them across every internal document.
APAC teams running Atlassian stacks (Jira + Confluence) hit the custom-scheme block almost daily.
Use case: Convert custom scheme URLs into universal HTTPS links once, paste them anywhere, and stop manually re-explaining how to open the app.
Distributed and remote teams across every region run into the same problem: deep links that work in one app break the moment they leave it.
Use case: Use Shortlink to wrap any custom scheme URL into an HTTPS link that works in every tool your team uses.
A URL scheme is the protocol prefix at the start of a URL, like https:// or slack://. Apps register custom schemes with the operating system so that links using their scheme open the app directly. Examples include obsidian://, zoom://, notion://, and vscode://.
Most apps publish their URL scheme in their developer documentation. On macOS you can also inspect an app’s Info.plist file under CFBundleURLSchemes. On iOS the same key is in the bundle. The Shortlink registry above documents the schemes for 50+ popular apps.
Slack uses the slack:// scheme. Common formats include slack://channel?team=T0001&id=C0001 to open a channel and slack://user?team=T0001&id=U0001 to open a DM. These links work on macOS, Windows, iOS, and Android Slack clients.
Zoom registers two schemes: zoommtg:// (used by the legacy desktop client) and zoomus:// (used by newer clients). The most common format is zoommtg://zoom.us/join?confno=123456789 to join a meeting by ID.
Use the vscode:// scheme. Examples: vscode://file/path/to/file.js to open a specific file, vscode://settings to open settings, or vscode://vscode.git/clone?url=https://github.com/user/repo to clone a repository.
Browsers can launch custom schemes via the OS handler, but most websites strip non-HTTP(S) URLs from rendered content for security. Pasting slack:// or obsidian:// into Notion, Confluence, or an email body usually results in plain text, not a clickable link. Wrapping the scheme in an HTTPS URL with Shortlink solves this.
Use the main Shortlink converter to turn any slack://, obsidian://, zoom:// or notion:// URL into a universal HTTPS link.