Marketplace Integrations
Discover, authorize, monitor, and disconnect apps that extend an Eigenn team workspace.
The App Marketplace is the control center for connecting Eigenn to accounting systems, payments, communication tools, automation platforms, storage services, CRM tools, and MCP clients.
What the Marketplace Helps You Do
- browse official and approved external apps
- search and filter by capability, category, connection method, or availability
- review permissions and setup requirements before connecting
- see which apps are installed for the current team
- inspect recent sync health when an app records activity
- update settings, disconnect access, or report an app
Browse the Catalog
- Open Apps.
- Review the featured integrations.
- Search by app name or description.
- Narrow the catalog with:
- category
- official or external type
- active availability
- capability
- authentication method
- installed state
- Open an app card for details.
The default featured set currently highlights Stripe Connect, Gmail, and QuickBooks Online when they are present in the catalog.
Understand App Types
Official apps
Official apps are bundled with Eigenn. Their setup can open an OAuth window, request a provider API key, accept an automation URL, or generate MCP configuration.
Examples of active official app definitions include Stripe Connect, QuickBooks Online, Xero, Slack, Gmail, Resend, Zapier, and supported MCP clients. Other definitions are marked beta or coming soon. Always trust the current badge in the marketplace over a static list.
External apps
External apps are OAuth applications created by a developer team. Only applications with approved marketplace status are shown to other users. Installing one grants the selected scopes through Eigenn's consent flow.
Review the developer name, website, scopes, screenshots, and install URL before allowing access.
Read the Detail Panel
Depending on the app, the panel can include:
| Detail | Why it matters |
|---|---|
| Connection method | Tells you whether the app uses OAuth, a provider key, a webhook URL, or MCP. |
| Availability | Distinguishes active, beta, and coming-soon coverage. |
| Capabilities | Describes the record types and actions the app is designed to use. |
| Provider scopes | Shows permissions requested from the connected service. |
| Before you connect | Lists prerequisites and mapping work. |
| Reacts to these events | Lists event names recognized by that app. |
| Activity | Shows recent sync outcomes when the connection records journal activity. |
An event badge is app metadata. It does not create a universal webhook subscription or payload contract.
Connect an App
- Select the correct Eigenn team.
- Open the app.
- Review its permissions and availability.
- Complete the displayed prerequisites.
- Select the install or connect action.
- Complete provider consent or enter the required configuration.
- Return to the marketplace and confirm the app is installed.
- Run a test or review the first sync before depending on the data.
For an accounting app, verify company or tenant selection and account mappings. For an inbox connection, verify the mailbox or labels being watched. For an automation app, send a harmless test event.
Monitor Sync Activity
Installed apps can show:
- connection date
- enabled state
- healthy, warning, error, or idle status
- synced and failed counts
- recent record direction and entity type
- recent provider error messages
Idle means no sync-journal activity is available. It is not the same as a successful provider test.
If data appears stale:
- confirm the connection is enabled
- inspect the latest failed activity
- compare provider permissions with the app requirements
- run the connection test or reconnect
- compare one source record with Eigenn
Disconnect and Revoke
Most official app disconnect actions remove the saved team connection. External app disconnect revokes the current user's tokens for that OAuth application. Gmail currently uses an enable or disable sync action, and Corinthian performs a paired remote uninstall.
Important limits:
- Disconnect is not documented as deleting already imported Eigenn records.
- Provider-side authorization is not universally revoked by the marketplace action.
- Other team members can have their own authorization to an external app.
For a complete security removal, disconnect in Eigenn, revoke Eigenn at the provider when appropriate, and review retained records.
Availability Boundaries
- Coming-soon apps are visible catalog plans, not usable integrations.
- Beta apps can change behavior and should be tested with representative records.
- A capability label does not guarantee every record field or direction.
- No single retry, signature, sync frequency, or disconnect rule applies to every app.
- Installing an app does not grant access to undocumented public API operations.