Skip to app details
Back to app library
APPNEURAL APP FAMILYAutomation & Integrations

Connections

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.

01 / OVERVIEW

See where it fits in your day.

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.

A LOOK INSIDEExample layout · sample content
Connected accounts
Connected accountsIllustrative configuration
01Google Search ConsoleExample
02WhatsApp Cloud APIExample
03RazorpayExample
02 / CAPABILITIES

Built around the work you do.

What Connections does for you.

01

Providers

Google, Meta, LinkedIn, Microsoft 365, Zoho, Razorpay, Stripe, Slack and more, each with what it needs.

02

Health checks

Daily identity checks and token refresh, with an email when a connection breaks or expires.

03

Token API

Other apps get a fresh access token with a secret key; refresh tokens never leave.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Connections. What you can do depends on your access in the app.

01

Add the provider's app

Paste the client ID and secret once, for one domain or for every domain.

02

Connect the account

Sign in with the provider, or save an API key that is checked first.

03

Keep it healthy

Act on broken and expiring connections first.

YOUR NEXT MOVE

Make Connections part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE1 items
P2VERIFIEDPUBLISHED
Overview

Purpose and boundaries

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.

Which external account is connected to which brand: provider definitions, OAuth and API-key connections with sealed tokens, refresh and health checks, reconnect links and a token API for the other catalogs.

APPNEURAL sign-in belongs to Auth; developer secrets belong to Secrets.

Priority
P2
Portfolio
Automation & Integrations
Capability
Automation & Integrations
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:12
Semantic inventory

Every number says what it counts

1Catalog itemstrackedEntityCount · catalog-api:live
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

connection schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

connections.appneurox.com DEPLOYED

connections.appneurox.com

Worker
connection-catalog
Health
HEALTHY
Last deployment
2026-11-18 14:03:12
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/connection-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app