Overview
How Selena AI connects to the systems your team already works in — what an integration does, how it is scoped, and what is available today.
Selena AI does its work inside your systems, not beside them. An integration is what makes that possible: it lets Selena read your live records — catalogs, estimates, customers, projects — and write results back where your team already looks for them, instead of handing you text to re-key.
That makes integrations foundational rather than optional. With none connected, Selena can still read a file you upload and draft a document from it. It cannot resolve a part against your catalog, price a real estimate, or write a line item anywhere.
What an integration gives Selena
Integrations differ in which system they reach, but each one grants some combination of the same four things:
| Capability | What it means in practice |
|---|---|
| Reference data | Catalogs and price books — the source of truth a detected or requested part resolves against, including your organization's own favorites |
| Transactional records | Estimates and their line items, customers, contacts, locations, projects, opportunities — read in plain language, without leaving chat |
| Writes | Creating and updating those records: an estimate, a bulk set of line items, a note, a customer |
| Your identity | Agent reads and writes use the connected user's own credentials, so permissions, visibility, and audit trails in the connected system stay exactly as they already are |
The last row is not a setting — it is how integrations are built. An agent cannot see or change anything the person asking could not already see or change. The exception is narrow and deliberate: an integration may hold an organization-level credential for setup validation and for background data sync, neither of which is an agent acting on a user's behalf.
Available integrations
Estimating and quoting
Your system of record for estimates — the catalog parts resolve against, and the place line items are written.
Accounting and ERP
No direct integration today. Accounting-sourced parts reach Selena through your estimating system where your organization has configured them, so they appear in parts search without a separate connection.
This is worth knowing when a part is missing. Parts search spans what the connected system exposes — your catalog, company favorites, and accounting sources. A part that lives only in a source your organization has not configured will not be found, and the fix is in the connected system rather than in Selena.
Something else
Integrations are built one system at a time, and which one comes next is driven by what teams say is blocking them. If your team estimates, purchases, or manages projects somewhere Selena does not reach yet, say so in the Selena AI Discord — naming the system and the workflow you would hand over is what moves it up the list.
How every integration works the same way
The connection model belongs to the platform, not to any one provider. Learn it once and the next integration behaves the same.
Two levels of connection
Both are required before anything works.
The organization connects the system
An admin points Selena AI at your instance and validates it once, in Dashboard → Integrations. This establishes which system your organization talks to. Credentials entered here prove the instance is reachable and yours; they are not what individual users authenticate with later.
Each user connects their own account
Individual users then authenticate with their own credentials, in Dashboard → Settings → Integrations. This is what makes Selena AI act as that user.
A user cannot connect before the organization is configured — their status will read
not_available. If everyone on your team is blocked at once, org-level setup is what
to check first; a single user failing while the team is fine is almost always their
own expired or rejected connection.
Status is reported at both levels
Each level carries its own status, and reading the right one is how you tell an organization-wide outage from one person's expired session:
- Organization status covers whether the system is configured, validating, failed validation, working, or was working and has stopped being reachable. While it is anything but working, no user connection helps.
- User status covers whether that person has connected, is connected, needs their session refreshed, or had their credentials rejected. It affects only them.
Exact status values are provider-specific — see WeSuite for the full tables, and Common Issues for what clears each one.
Disable and delete are not the same
Two ways exist to turn an integration off, and the difference matters:
- Disable keeps the organization's configuration and every user connection intact, but stops the integration from doing anything. Reversible without re-entering anything.
- Delete removes the configuration and all user connections. Turning it back on means running org setup again and having every user reconnect.
Prefer disable unless you specifically intend to unwind the whole thing.
Using an integration from an agent
Once connected, an integration is available to Selena AI's agents automatically. There is nothing to wire up per conversation and no agent to pick — asking for a part, an estimate, or a customer uses your connection.
Two behaviors are shared across integrations, and both exist to keep a wrong value out of a real record:
Ambiguity stops and asks. When a part, customer, or folder is resolved from search text rather than an exact identifier, Selena returns the candidates for you to choose from instead of picking one. That holds even when there is a single match — silently guessing is how a wrong item ends up priced into a live quote.
Failed writes are never retried automatically. Selena reports the error and stops, which leaves the decision with you. Whether repeating a request is safe depends on the write, and the connected system's own guarantees decide it — the intro lists which writes are safe to repeat and which can produce a duplicate. When a write fails or its outcome is unclear, check the record in the connected system before asking again.
When something is not working
Every integration has a section in Common Issues, organized by symptom — setup and validation, a whole team blocked, one user's connection, records that cannot be found. Start there.
Whatever you are looking at, bring three facts: the workflow, whether it affects one user or everyone in the organization, and the record involved. Those three narrow an integration problem down fastest.
Invite your Team
Add members to your Selena organization so your team works in the same place — how invitations work, what Admin and Member can each do, and how to manage people after they join.
WeSuite
Connect Selena AI to WeSuite so agents can search parts, build estimates, and write BOM results back into your system.