Integrations
Trelium agents connect to the systems you already use, through an API where one exists and through the web interface where it does not. Nothing is migrated or replaced.
Trelium connects to your tools in one of two ways: through an API when the system offers one, or through the browser when it does not. In both cases the agent works inside the system you already run, so you do not move data, replace software, or change how your team uses it.
What an integration means in Trelium
An integration is the route an agent uses to reach one of your existing systems. It is not a copy of that system and it is not a replacement for it. Your ERP stays your ERP, your accounting software stays your accounting software, and the records stay where they are.
Because the agent reaches into each system directly, one task can span several of them. The agent reads from one, checks another, and writes to a third, using the same access your team would use.
Two ways to connect
Trelium uses an API connection where a system offers one. Where a system has no API, a browser agent operates its web interface the way a person would.
| API-based | Browser-based | |
|---|---|---|
| How the agent reaches the system | Through the system's published API | Through the system's web interface, by navigating pages and filling in fields |
| Good for | Structured reads and writes, and systems that expose the data you need | Systems with no API, or where the API does not cover what your team does by hand |
| Where it can break | The API does not expose a field or action you need | The web interface changes in a way the agent cannot make sense of, which stops the run |
| What it depends on | What the API allows | What a logged-in user can see and do on screen |
The right one depends on what the system offers. For more on how browser agents work, see Browser Agents. When something does break, the run stops and surfaces as an exception instead of guessing. See Validation & Exceptions.
What a connection lets an agent do
Once a system is connected, an agent can read records and write updates within the access the connection has. What it can do in a given system depends on that system and on how the connection is set up, so ask during setup if you need to confirm a specific action in a specific system.
Systems by category
The Trelium integrations directory lists the full catalog across CRMs, ERPs, email, accounting, e-commerce, and more, and is kept current there. Some examples of the kinds of systems by category:
| Category | Examples |
|---|---|
| ERP | NetSuite, SAP, Odoo, Acumatica, Epicor Prophet 21, Infor M3 |
| Order management | Syncore, Printavo, ShopWorks |
| Accounting | QuickBooks, Xero, Sage Intacct, Bill.com, Avalara |
| CRM | HubSpot, Salesforce, Zoho |
| E-commerce | Shopify, WooCommerce, BigCommerce |
| Payments | Stripe, PayPal, Square |
| Shipping | UPS, FedEx, DHL, USPS, ShipStation |
| Communication and support | Gmail, Outlook, Slack, Microsoft Teams, Zendesk |
| Spreadsheets, storage, and notes | Google Sheets, Google Drive, Dropbox, Box, Airtable, Notion |
The directory does not say, for each listed system, whether it is reached by API or by browser. Check the directory entry or ask the Trelium team about the system you care about. If your system is not listed, ask as well. The browser path means a listing is not a hard requirement.
Example: a purchase order across three systems
Say a purchase order arrives by email. A single agent can handle it across systems:
- The agent reads the email and pulls out the customer, items, quantities, and requested date.
- It checks your accounting system for the customer record, item details, and open balances.
- It enters the order in your order management system.
- The run is saved in the agent's Activity log, with each step it took, so your team can trace the work.
The order only makes sense once all three systems agree. The inbox holds the request, the accounting system holds the customer and financial facts, and the order management system holds the commitment. An agent limited to one of them would leave your team to carry information between the others by hand. Working across all three is what removes that step.
Automated actions and human approval
Connecting a system does not mean the agent acts unsupervised. Reading and writing are things the agent does. Approval is a decision a person makes. Where your workflow calls for a person to approve a step, such as confirming an order before it is entered, the agent stops and waits for that approval. See Human in the Loop for how approvals work and How Trelium Works for how checkpoints fit into a run.
Where to go next
Connecting Systems
How systems are connected and what the setup involves.
Browser Agents
How an agent works inside a web interface when there is no API.
Human in the Loop
Where approvals fit when an agent reads and writes in your systems.
How Trelium Works
The overall picture of agents, systems, and approvals.
Agents & Workflows
What a Trelium agent is and how its workflow works. Covers the four parts of a workflow (trigger, steps, rules, and review points), how fixed steps and AI fit together, and an example from start to finish.
Connecting Systems
How your tools get connected to Trelium. Covers the six ways in, what your team does for each, and what a connected agent can do.