Integrations
Connect external systems through the App Marketplace, review their permissions, and manage connection health safely.
Eigenn integrations connect payment, accounting, communication, automation, and AI tools to a team workspace. Each app has its own connection method and data responsibilities, so review the app details before authorizing access.
Find the Right App
- Open Apps from the main navigation.
- Search by app name or browse the category sections.
- Filter by category, capability, connection method, availability, or installed state.
- Open an app to review its details before connecting it.
The marketplace combines:
- Official apps maintained in Eigenn
- External apps that have been approved for the marketplace
Only approved external apps appear in the catalog. Availability badges distinguish active, beta, and coming-soon entries. A coming-soon entry describes planned coverage; it is not a working connection.
Review Access Before Connecting
The app detail panel can show:
- the connection method, such as OAuth, API key, webhook, or MCP
- the capabilities the app can use
- provider scopes requested during authorization
- setup prerequisites
- events the integration reacts to
- configuration fields and client snippets
- documentation and availability status
Do not infer permissions from an app name alone. For example, an accounting connection can read customers while also writing invoices or payments. Confirm the displayed scopes and capability labels against the workflow you intend to enable.
Connection Methods
| Method | What to expect |
|---|---|
| OAuth | Eigenn opens the provider's consent flow and stores the resulting connection for the selected team. |
| API key | You enter a provider credential in the app's settings. Use a restricted provider key when possible. |
| Webhook | You supply a public destination URL or complete an automation-platform subscription flow. |
| MCP | You copy a client configuration or connect to Eigenn's remote MCP endpoint. |
External OAuth apps use Eigenn's consent screen. The consent request is limited to the application's registered redirect URL and scopes. Public OAuth clients must use PKCE.
Check Connection Health
Installed apps can expose:
- when the connection was installed
- whether the connection is enabled
- a healthy, warning, error, or idle state
- recent inbound or outbound sync activity
- synced and failed record counts
- the latest provider error
An Idle state means the app is installed but has no recorded sync activity. It does not prove that a live provider connection has been tested.
Before relying on imported data:
- Open the installed app.
- Review its activity and last successful sync.
- Resolve recent failures.
- Compare a small set of source records with Eigenn.
- Run the integration's test action when one is available.
Disconnect an App
Disconnect behavior depends on the app type:
- Disconnecting most official apps removes the saved team connection in Eigenn.
- The Gmail control currently enables or disables mailbox sync instead of following the same removal flow as other official apps.
- Disconnecting an external OAuth app revokes the current user's Eigenn-issued access for that application.
- Disconnecting the Corinthian bridge also tears down its paired remote connection.
Disconnecting is not documented as deleting customers, invoices, transactions, or documents that were already imported. It also does not universally guarantee that the provider-side authorization was revoked. Review retained records in Eigenn and remove Eigenn from the provider's connected-app settings when your security policy requires both actions.
Security Practices
- Connect apps only from the team that should own the data.
- Grant the smallest provider and Eigenn scopes that support the workflow.
- Keep provider API keys out of browser code, chat, screenshots, and shared documents.
- Reconnect an app after changing provider permissions so the saved authorization matches the new scope.
- Treat webhook URLs and MCP configuration as credentials when they contain secrets or grant access.
- Review installed apps when a team member changes roles or leaves the organization.
Current Boundaries
- App capabilities are integration-specific; no single event, retry, sync, or disconnect contract applies to every marketplace app.
- A marketplace event label describes what an app can react to. It is not a universal public webhook schema.
- The public REST API and MCP endpoint are separate from marketplace installation. Installing an app does not create a general-purpose API key.
- External apps are visible only after approval, and their availability depends on the application being active.