Deeplinks
The meetilypro:// URL scheme and which actions are gated by the off-switch.
Meetily registers a meetilypro:// URL scheme. Deeplinks are enabled by default and, unlike the rest of Integrations, are not gated behind the master Integrations switch and are not Pro-gated - it's the one integration capability available out of the box. A deeplink never directly drives capture; the recording actions only ask the app to act, and still require their own gates plus an in-app confirmation.
Actions
| URL | Action | Gated? |
|---|---|---|
meetilypro://meeting/{id} | Open a meeting in the app | Ungated |
meetilypro://record/start | Request that recording start | Gated: requires the gateway enabled and Pro, and only emits an in-app confirm request; it never starts capture directly |
meetilypro://record/stop | Request that recording stop | Gated: same as record/start |
meetilypro://license/activate?key=KEY | Activate a license | Ungated by design; the key is never logged |
Other actions, such as record/pause, are ignored.
How gating works
The deeplink_enabled flag defaults to true and is independent of the master Integrations enabled flag - it's on by default and not Pro-gated. But record/start and record/stop additionally require the gateway to be enabled and the Pro license, and they surface an in-app confirmation. A URL can never start or stop capture on its own.
A deeplink is a request, not a command
record/start and record/stop emit an in-app confirmation and never drive capture directly. license/activate stays ungated on purpose so a locked-out user can still activate a license.
Activation reports an accurate result
The license/activate deeplink shows a success toast only when the key actually activates the license (active or in grace). An inactive, expired, or hard-blocked key shows an error toast, not a false "PRO license activated". Confirmation toasts auto-dismiss after a few seconds.
Last updated on