Read
Retrieve authorized information.
A ServAI connector can expose one or more capability depths. Deep Action is shown only when the exact provider workflow has a process-aware, permission-aware execution adapter. A catalogued connector, API route or n8n workflow does not automatically imply Level-4 execution.
Retrieve authorized information.
Draft a governed change without external mutation.
Propose the action and keep authority with the user.
Execute only through an accepted provider-specific business-process adapter.
Browse 1,000 published connector routes. Priority systems use native ServAI adapters; SaaS and long-tail applications use governed n8n workflows or scoped API/webhook routes. A connector becomes usable only after tenant configuration, policy admission and health checks.
Every card opens a full ServAI detail page. The original 60 remain the reviewed baseline; the wider catalogue contains real named systems that can be admitted through governed n8n, API/webhook or enterprise adapter routes after tenant-specific review.
“Published” means the route has a ServAI detail page. It does not mean that a customer connection is active. Operational status is always tenant-specific.
ServAI can probe tenant readiness, show missing authentication/scopes/features/data, discover canonical actions, materialize them into the organization capability graph, and prefer certified/regional-compatible adapters without granting credentials or authority.
Bind an organization connection without exposing credentials to role, mission or marketplace metadata.
See AVAILABLE, PARTIAL, UNAVAILABLE or UNKNOWN action capability with exact blockers.
Adapter certification covers compatibility, requirements, tests, provenance, versioning and revocation—not automatic installation.
Regional profiles can add locale, evidence, data, residency and document requirements without claiming legal compliance.
Native ServAI adapters, governed n8n workflows, APIs and enterprise connector packs can support different depths: Read, Prepare, Recommend or Deep Action. Catalogued does not mean customer-connected—or Level-4 actionable. Every connection is scoped, admitted and health-checked before use.
Credentials and scopes belong to the customer connection.
Connected and verified sources are distinct from merely catalogued integrations.