Build correctly formatted slack://, obsidian://, zoom://, notion://, and figma:// deep links from a guided form. Get both the raw scheme URL and a universal HTTPS Shortlink that works in tools that strip custom schemes.
Find this in your Slack URL: app.slack.com/client/T0001/...
In Slack, right-click a channel → Copy link.
Optional. Targets a specific message.
Fill in the required fields…—A deep link is a URL that opens a specific view inside a desktop or mobile app rather than landing on a generic homepage. Custom URL schemes like slack://, obsidian://, and notion:// are how apps register themselves with the operating system to handle their own links.
The catch: while the OS knows how to open these schemes, most content platforms (Notion, Confluence, Gmail, GitHub) refuse to render them as clickable links. Wrap the deep link in an HTTPS URL via Shortlink and it works everywhere.
Reference for the most-used custom URL schemes. Use the builder above to generate any of these without hand-crafting the URL.
| App | Format |
|---|---|
| Slack | slack://channel?team={team_id}&id={channel_id} |
| Obsidian | obsidian://open?vault={vault}&file={note_path} |
| Zoom | zoommtg://zoom.us/join?action=join&confno={meeting_id} |
| Notion | notion://www.notion.so/{page_id} |
| Figma | figma://file/{file_key}/{name} |
| Linear | linear://issue/{TEAM-123} |
| VS Code | vscode://file/{absolute_path}:{line}:{col} |
Custom scheme URLs only render as clickable when the platform that displays them allows non-standard schemes. Notion, Gmail, GitHub, Linear, and most enterprise wikis don’t. Wrapping the deep link in an HTTPS URL solves this without changing the destination.
Shortlink encodes the original scheme URL into the path of an https://shortlink.studio/... URL using stateless LZ compression. The wrapped link works in any context that allows HTTPS links; clicking it triggers a client-side redirect to the original scheme URL, which the OS hands off to the registered app.
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.
Slack channel deep links use the format slack://channel?team={team_id}&id={channel_id}. The team ID starts with T (e.g. T0001), and the channel ID starts with C. You can find both in the URL when you open Slack in a browser, or by right-clicking a channel and selecting Copy link.
Obsidian uses the obsidian:// scheme. The most common format is obsidian://open?vault={vault_name}&file={note_path} to open a specific note. Advanced URI plugin extends this with obsidian://advanced-uri for jumping to headings, blocks, or running commands. Both formats work across macOS, Windows, Linux, iOS, and Android.
The native zoommtg:// scheme is stripped by Notion. Two options work: paste the standard https://zoom.us/j/{meeting_id} URL (opens in browser, then app), or use this builder to generate a zoommtg:// link, wrap it in a Shortlink, and paste the Shortlink into Notion. Both render as clickable links.
Figma deep links use the figma:// scheme to open a file directly in the desktop app. The format is figma://file/{file_key}/{file_name} where the file key is the alphanumeric ID from the Figma URL (figma.com/file/<key>/...). Add ?node-id=<id> to open at a specific frame.
Open the page in Notion and copy its URL. The page ID is the 32-character alphanumeric string at the end (e.g. notion.so/Page-Title-abc123def456...). The deep link format is notion://www.notion.so/{page-id}. This builder extracts the ID automatically when you paste the full URL.
Use the main Shortlink converter to turn any slack://, obsidian://, zoom:// or notion:// URL into a universal HTTPS link.