Intry

Push notifications

FCM, APNs, and Knock delivery in the Intry mobile app.

Overview

Entry alerts are delivered through Knock workflows to registered Device tokens. The app registers tokens with Core after login.

Runbook: docs/PUSH_NOTIFICATIONS.md.

Registration flow

  1. User logs in (Clerk or legacy JWT).
  2. App obtains FCM/APNs token from OS.
  3. POST /devices/register with token, platform, and device metadata.
  4. Core stores Device row linked to User.

User actions

When a push arrives, the resident taps Approve or Deny. The app calls /access/* endpoints; Core signals the telephony provider to release the door or hang up.

The approval window is approximately 30 seconds.

Fallback channels

If push fails or user enables fallbacks (set in app settings):

  • SMS with approve/deny links
  • Voice call to phone on file

See Notifications architecture.

Troubleshooting

IssueCheck
No pushOS notification permissions; Device.isEnabled; DND mode
Delayed pushKnock workflow logs; device token freshness
Approve doesn't open gateCall may have expired; telephony provider logs

Last verified: 2026-06-21 (commit 293c4a7)

Intry App overview

Expo mobile client for residents — structure and Core integration.

Deep links

Universal links and app URL schemes for Intry mobile.

On this page

OverviewRegistration flowUser actionsFallback channelsTroubleshooting