One shape every integration. Pluggable providers behind.
Every connector is a type (ecommerce, ticketing, PIM, CRM) with pluggable providers. Agents declare which types they need; the kernel enforces explicit grants. Build your own with the framework — same shape every time.
Ecommerce
Read orders, customers, catalogue; write back line-item notes, order edits, flagged returns.
- ShopifyLive
- BetterCommerceLive
- BigCommerceBeta
- Magento / Adobe CommerceComing
- WooCommerceComing
Customer support & ticketing
Pull threads, drafts, customer context; post drafts under review, resolve, tag.
- ZendeskLive
- FreshdeskLive
- IntercomComing
- HubSpot ServiceComing
ERP & accounting
Read invoices, inventory, GL; draft reconciliations and amortisation entries under approval.
- NetSuiteLive
- Sage IntacctBeta
- XeroComing
- SAP B1Coming
PIM & catalogue
Read SKU attributes, media, brand guidelines; propose SKU copy and structured attributes.
- Akeneo PIMBeta
- SalsifyComing
- Custom PIM via RESTLive
CRM & marketing
Read profiles, segments, campaign history; draft personalised messages for review.
- KlaviyoLive
- HubSpot CRMBeta
- SalesforceComing
- BrazeComing
Communications
Send and receive email, read inboxes, draft responses under policy.
- Microsoft 365Live
- Google WorkspaceComing
- SMTP (any)Live
- SlackComing
- TeamsComing
Fulfilment & logistics
Read shipments, carrier status; proactively message customers on delay or exceptions.
- ShipStationBeta
- WMS (REST)Live
- ShippoComing
Data & analytics
Read customer snapshots, embeddings, historical metrics; write operational outcomes back.
- SnowflakeBeta
- DatabricksComing
- BigQueryComing
- Postgres (any)Live
Knowledge
Vector-indexed documents bound per agent. Permission-aware retrieval across sources.
- SharePointBeta
- ConfluenceComing
- NotionComing
- File uploadLive
Can't see yours? Most REST-based systems can be wired in a week via the framework.
The pattern you build once, then reuse.
Writing a new connector takes about a week of focused work. Reusing an existing type for your own vendor takes a day.
One connector type
A connector is a type (ecommerce, ticketing, PIM…) with a stable contract — not a bespoke SDK per vendor.
Pluggable providers
Each type has multiple provider implementations. Swap Shopify for BetterCommerce without touching the agent.
Multi-tenant from day one
Credentials are tenant-scoped. The kernel brokers access per invocation. Agents never see raw secrets.
Explicit grants per agent
An agent declares the connector types it needs. The deploy wizard refuses incomplete bindings — no silent runtime errors.
Need a connector that isn't listed?
If it has an API, we can wire it. Design partners get priority on new connector builds — tell us which systems you need and we'll scope the work.