Providers
Google, Meta, LinkedIn, Microsoft 365, Zoho, Razorpay, Stripe, Slack and more, each with what it needs.
Every connected account, and who looks after it
See which Google, Meta, payment and messaging accounts are connected to each brand, and keep them working.
36 provider definitions (Gmail, Drive, Calendar, Search Console, Analytics, YouTube and Business Profile from Google; Facebook Pages, Instagram and the WhatsApp Cloud API from Meta; LinkedIn, X, Microsoft 365, Zoho CRM, HubSpot, Shopify, WooCommerce, Razorpay, Stripe, Cashfree, Slack, Discord, Telegram, Notion, GitHub, Cloudflare, Mailchimp, Brevo, Resend, MSG91, Twilio, Gupshup, Dropbox, Zoom, any OAuth2 app and any API key) say how each signs in, where to create the app or key and what approval the provider needs. The owner saves one OAuth app per provider group, for a domain or platform-wide, with the client secret sealed. Signing in uses a single-use state, a nonce cookie and PKCE, and the tokens are sealed with VAULT_KEY; API keys are checked against the provider before they are saved. Each connection records the account, scopes granted, who connected it and when, the responsible person and its status (active, expiring, expired, error, revoked). Crons check identities daily and refresh tokens every six hours; a status change emails the responsible person a single-use /r/<token> reconnect link (7 days), alerts the team and sends a webhook. Other catalogs call POST /api/v1/connections/<id>/token with a secret API key and get a fresh access token, refreshed under a lock; refresh tokens never leave, and every hand-out is logged.
What Connections does for you.
Google, Meta, LinkedIn, Microsoft 365, Zoho, Razorpay, Stripe, Slack and more, each with what it needs.
Daily identity checks and token refresh, with an email when a connection breaks or expires.
Other apps get a fresh access token with a secret key; refresh tokens never leave.
A suggested path for Connections. What you can do depends on your access in the app.
Paste the client ID and secret once, for one domain or for every domain.
Sign in with the provider, or save an API key that is checked first.
Act on broken and expiring connections first.
Live host, inventory, governance, health checks, verification, dependencies and history.
36 provider definitions (Gmail, Drive, Calendar, Search Console, Analytics, YouTube and Business Profile from Google; Facebook Pages, Instagram and the WhatsApp Cloud API from Meta; LinkedIn, X, Microsoft 365, Zoho CRM, HubSpot, Shopify, WooCommerce, Razorpay, Stripe, Cashfree, Slack, Discord, Telegram, Notion, GitHub, Cloudflare, Mailchimp, Brevo, Resend, MSG91, Twilio, Gupshup, Dropbox, Zoom, any OAuth2 app and any API key) say how each signs in, where to create the app or key and what approval the provider needs. The owner saves one OAuth app per provider group, for a domain or platform-wide, with the client secret sealed. Signing in uses a single-use state, a nonce cookie and PKCE, and the tokens are sealed with VAULT_KEY; API keys are checked against the provider before they are saved. Each connection records the account, scopes granted, who connected it and when, the responsible person and its status (active, expiring, expired, error, revoked). Crons check identities daily and refresh tokens every six hours; a status change emails the responsible person a single-use /r/<token> reconnect link (7 days), alerts the team and sends a webhook. Other catalogs call POST /api/v1/connections/<id>/token with a secret API key and get a fresh access token, refreshed under a lock; refresh tokens never leave, and every hand-out is logged.
APPNEURAL sign-in belongs to Auth; developer secrets belong to Secrets.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
connections.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.