Permissions
Allow, ask or deny on every individual tool inside every connector.
Integrations
A workforce can only work where it can reach.
An agent that can’t touch your systems can’t do a job. It can only talk about one. Connectors are what turn a capable model into an agent that gets work done.
Checking for something specific? The full capability list →CountConnector libraryState
101Live connectors across core business systems and the wider ecosystemLive
09In active development, customers influence the orderBuilding
ANYYour own APIs, lifted into the platform on requestOn ask
Every connector arrives on the same permissions · the same credential handling · the same approvals · the same audit trail · adding reach never means adding risk · every connector arrives on the same permissions ·
01 · Why this page matters more than it looks
Every connector arrives on the same plane of control
This is the difference between a workforce and a pile of integrations. However a connector got here, hand built by us or pulled from the wider ecosystem, it lands on the same permissions, the same credential handling, the same approvals and the same audit trail. Adding reach never means adding risk.
Credentials
Held by the platform, never delivered to the model, revocable in one place.
Approvals
Anything consequential pauses and asks a person, in the channel your team uses.
Audit
One ledger. Who asked, which agent, which tool, which credential, what happened.
02 · Live now
The systems your business already runs on.
Every integration is configured for real operational work, not just authenticated. Ready to work inside your agents from day one, with the retail stack hand tuned first.
ShopifyCategoryConnectorState
COMMERCEShopify orders, products, inventory, customers and analyticsLive
MARKETINGKlaviyo email and SMS performance, segments, flow dataLive
SUPPORTGorgias tickets, satisfaction, response and resolution dataLive
INVENTORYCin7 stock levels, sell through, supplier lead timesLive
WHOLESALEDotapparel B2B catalogue, orders, account performanceLive
COMMSSlack outputs, alerts, digests and approvals in your channelsLive
COMMSGmail drafts, sends and inbox monitoringLive
MARKETINGMeta Ads campaign performance, spend, return, audiencesLive
MARKETINGGoogle Ads search and shopping campaign dataLive
ANALYTICSGoogle Analytics traffic, funnels and behaviour dataLive
FINANCEXero profit and loss, cashflow, invoices, reconciliationLive
FINANCEStripe payments, refunds, disputes and payoutsLive
+ 89More across the wider ecosystemLive
03 · Custom fit
Any vendor with an API becomes a tool
Three ways to add a connector, at three levels of depth. Every one of them, wherever it came from, flows through the same permission, credential and audit controls.
A · Breadth
Standard plug in
If a vendor offers a standard AI tool integration, we plug it in. Credentials and approval rules still flow through us, even when the connector came off the shelf.
B · Depth
Native package
Hand tuned packages for the systems our customers live in. Curated actions, polished behaviour, and workflows built around how retail actually runs.
C · Custom fit
Your own APIs
An internal warehouse system, a customer specific endpoint, a partner API. We lift it in and the agent treats it like any other tool.
Days, not quarters.
Every connector follows the same standard pattern, so adding a new one for a customer is a configuration exercise rather than a rebuild.
04 · How it works
One click connections, on an open standard
Lifter uses the Model Context Protocol, an open standard that gives agents secure, structured access to external tools and data. Connectors are native, not fragile webhooks or custom scripts. Because the standard is open and growing, the library expands through our releases and through the wider ecosystem, without you waiting on our roadmap.
Step 01
Select your integration
Browse the catalogue and choose the systems you want your agents to reach.
Step 02
Authenticate once
A standard sign in flow. Credentials are encrypted, held by the platform, and never stored in plain text or handed to a model.
Step 03
Set permissions
Choose exactly what each agent can read and write, tool by tool. Nothing moves without the stance you set.
Step 04
Your agents are live
From that point they can pull data, take actions and surface insight across your connected stack, inside your rules.
05 · In development
What we’re building next
Actively in development. Customers influence the order, so if something here’s critical to your stack, tell us.
CategoryConnectorState
COMMERCEBigCommerceBuilding
COMMERCEWooCommerceBuilding
MARKETINGTikTok AdsBuilding
MARKETINGActiveCampaignBuilding
FINANCEMYOBBuilding
COMMSMicrosoft TeamsBuilding
COMMSOutlookBuilding
INVENTORYUnleashedBuilding
CRMPipedriveBuilding
Built on request
Don’t see what you need?
Connectors that don’t exist yet are defined with you during onboarding, and you can request more at any time. If a system is critical to how your business runs and it isn’t on the list, tell us and we’ll build it.