Apps connect Stackyapper to the systems your company already operates. Each app
defines its authentication method, available tools, access model, and current
support level.
Which apps are supported
The Apps page in the portal is the live catalog for your workspace,
covering systems such as PSA, RMM, documentation, finance, collaboration, and
security tools. The default Your apps view lists apps enabled, connected,
or granted to you in the selected workspace; search, or use the Category,
Scope, and (for owners and admins) Availability filters to find more.
Each app row keeps Connection, Tools, Auth method, and Skills in
consistent positions. Open an app and expand Integration evidence for its
testing stage. Private apps use the same row layout in their own section.
Owners and admins can select Add app to browse services, import an API
or MCP server, or build a connector with their agent. See
Build with Stackyapper to choose between a
connector, a reusable read tool and an interactive view.
If a system you need is not listed, see
Build a custom connector or Request an app.
See tool updates
When an app adds tools, a new count appears beside Tools on its row.
Select Tools to see new and updated tools, plus removed tools when your
role permits viewing that history. The list reflects your access in the
selected workspace. Owners and admins can inspect the app's management inventory.
Updates appear after Stackyapper records a changed tool inventory. Opening
Apps does not force a provider refresh, so an unrecorded provider change will
not appear yet.
The first visit establishes a starting inventory. Later counts describe
changes since you last read the app's complete change list; use Load more changes
when there are additional pages. If the inventory changes while you are
reading, reopen the list to see the current update. An unavailable update
check is shown explicitly rather than as zero new tools.
Reading updates does not grant access or approve tool calls. Automatic tool
review, your existing permissions, and call confirmations still apply. See
App status and ownership for the meaning of the
other row labels.
Start with one useful system
Choose an app that can answer a small, read-only question your team already
asks. Connect it, grant only the required read tools, and confirm the result in
Audit before expanding access.
Before connecting, confirm:
Whether the app uses an organization connection or a personal connection,
and which account should own the credential.
Whether the credential is limited to the intended company, tenant, or site.
Which read tools are needed for the first workflow.
Who will respond if the connection later needs attention.
What connection does not do
Connecting an app supplies the credential or authorization Stackyapper needs.
It does not automatically grant every user every tool. App availability,
workspace policy, groups, user grants, and restrictions determine effective
access.
Understand access
Learn how app availability and user policy combine.
Find the reference for an app
Open Apps, search for the provider, and open its connection details.
Configuration guidance appears alongside the fields that require it, together
with the app’s authentication method, required fields and prerequisites,
tenant boundaries, available tools and their risk classification, confirmation
requirements, and known setup limitations.
Request an app
If an app is not present, select Request an app from the empty search
result. It opens an email to Stackyapper support; include the provider name, the business workflow, the tenant boundary, and the
smallest set of operations required. Do not send credentials or API keys in the
request.
Support information to collect
When reporting an app problem, include the app name, its visible connection
state, the approximate time of the failed attempt, the tool name if known, the
Audit outcome and request identifier, and whether the connection is
organization-owned or personal. Never include secret values, authorization
codes, or full provider responses. For the escalation path, see
Troubleshooting.
In this section
Build a custom connector
Use your agent to create private MCP tools for a supported API (Beta).
Connect RingCentral
Create a RingCentral developer app and connect Phone, Chat, and Admin.
Google Workspace connected accounts
Connect multiple Workspace accounts and manage their permissions and data.
Microsoft 365 and Graph connections
Choose reviewed workloads and permissions for personal or application access (Beta).
App status and ownership
The connection, availability, maturity, and ownership labels shown in the
portal.
Portable artifacts
Hosted artifact pages and portable backups for supported AI clients (beta).