Apps and integrations
Connect an account, choose it for the right job and inspect connection outcomes.
An app connection lets Era perform operations you can access in another service. Sales email, calendars, external orders and other jobs can use different accounts. Connecting does not itself mean data synchronization has started.
App guide
Catalogue, accounts, tools and operations.
Account settings
Default accounts and recorded connections.
Where to find it
Web: Apps, /apps; desktop: Business → Apps. Settings → Organization → Apps (/settings/apps) manages installed accounts. Inspect connections and supported operations/details on each app record.
Choose the app
Open it in the catalogue and complete the offered OAuth sign-in or key setup. Typing its name does not establish a connection.
Choose account and scope
Select a personal or permitted shared account. Use distinguishable labels for sales, finance or info accounts.
Check the result
Test connection state and inspect tools. Reconnect, pause or remove when needed; separately check accounts used by agents and workflows.
Which account is used?
In my chats with Era selects your personal chat default. An agent or workflow can use its own selected account. An @ mention supplies context, not new access. Sending externally differs from preparing a draft and needs the applicable approval.
MCP in two directions
Settings → AI → MCP (/settings/integrations/mcp) adds outside servers into Era. Enable the server in an agent’s Apps & tools selection. Apps → MCP supplies the URL/key for another client to connect to Era; see MCP setup.
Connections do not widen access
apps.manage governs app management; target-module permissions govern record operations. A shared connection does not grant workspace administrator access.
Ask Era
Show connected accounts and apps needing sign-in again.
Prepare a reply draft from the sales account; do not send it yet.Continue with the integration catalogue, connection questions and external order/shipping work.