Integrations
Connect external systems through the App Marketplace, examine 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. Read the app details before you authorize 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 and read its details before you connect it.
The marketplace combines:
- Official apps maintained in Eigenn
- External apps that Eigenn approves 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.
Examine Access Before You Connect
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 and also write invoices or payments. Confirm the displayed scopes and the capability labels against the workflow that you want to turn on.
Connection Methods
| Method | What to expect |
|---|---|
| OAuth | Eigenn opens the provider's consent flow. Eigenn then stores the new 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 covers only the application's registered redirect URL and scopes. Public OAuth clients must use PKCE.
Check Connection Health
Installed apps can show:
- the installation date of the connection
- whether the connection is on
- 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 shows an installed app with no recorded sync activity. It does not prove that anyone tested a live provider connection.
Before you depend on imported data:
- Open the installed app.
- Examine 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:
- When you disconnect most official apps, Eigenn removes the saved team connection.
- The Gmail control now turns mailbox sync on or off. It does not use the same removal flow as other official apps.
- When you disconnect an external OAuth app, Eigenn revokes the current user's Eigenn-issued access for that application.
- When you disconnect the Corinthian bridge, Eigenn also tears down its paired remote connection.
The documentation does not say that disconnection deletes customers, invoices, transactions, or documents that Eigenn already imported. Disconnection also does not always guarantee that the provider revoked its authorization. Examine the records that stay in Eigenn. Then remove Eigenn from the provider's connected-app settings when your security policy needs both actions.
Security Practices
- Connect apps only from the team that must 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 you change provider permissions, so that 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. An app installation does not create a general-purpose API key.
- External apps are visible only after approval. Their availability also depends on an active application.