Connecting your apps
How to connect your CRM, accounting, and other tools to AMOS, the difference between personal and shared connections, and where your credentials are kept.
AMOS works with the tools you already run. Each app you connect becomes a set of governed, scoped tools the AI can call, rather than a screen it has to scrape.
What you can connect
CRM, finance and accounting, ERP, documents, databases, marketing tools, internal apps and APIs. In AMOS Desktop, start with the accounting, payments, CRM or sales tool that matters most for your first outcome.
How connecting works
- OAuth apps (for example QuickBooks and GitHub): AMOS gives you a sign-in link for the provider. You approve access on the provider's own consent screen in your browser, and the platform stores the result in the AMOS connections vault. No password or secret passes through chat. The link expires after about ten minutes and works once.
- API-key services: some services connect with an API key instead of a sign-in link.
- Your own OAuth app: a company can register its own OAuth2 app for a provider so AMOS can connect to it.
Personal and shared connections
- By default a connection is personal: it belongs to the person who approved it and is used only under their identity.
- An owner or admin can instead connect a shared service account. Automations use service accounts, and so do teammates who have not connected their own account.
Where your credentials live
Connection secrets and OAuth tokens stay in the AMOS Platform vault. Connector credentials are encrypted (ChaCha20-Poly1305) and are never returned to AMOS Desktop or to the AI model. The platform decides which connection a call may use, so the arguments of a call cannot redirect it to another company.
Limits
The Free plan includes two connected apps. Paid plans include more; see Pricing and plans.
Disconnecting
Owners can disconnect an app at any time. Disconnecting does not depend on the AI cooperating.