CONNECTIONSConnections for appneural.in
Connections For appneural.in.
APPNEURAL Connections records which external account is connected to appneural.in, who is responsible for it, and whether it still works, and hands other catalogs a fresh token when they need one.
Sign in
Team members use their own email and passcode. Owners use the Connections passcode for appneural.in.
36 providers, with what each needs
Google, Meta, LinkedIn, X, Microsoft 365, Zoho, HubSpot, Shopify, Razorpay, Stripe, Slack, Telegram, MSG91 and more, each with its sign-in type and the approval it needs.
Sign in once, sealed
OAuth sign-in with state and PKCE, or a key checked with the provider first. Tokens and keys are sealed; refresh tokens never leave the Worker.
Fresh tokens for other catalogs
Other catalogs ask for a token with an API key; it is refreshed when it is about to end, and every request is logged with the key that made it.
Broken accounts get noticed
A daily identity check per connection. When one breaks or nears its end, the responsible person gets a 7-day reconnect link, once.
connect.appneural.in Only appneural.in's connections, with the admin at the root. Sign-ins come back to /oauth/callback; reconnect links are /r/<token>.