Connector directory
OrgRelay ships with connectors for 90 business platforms. Each one uses the platform's official API with the company's own credentials, exposes read tools the AI can call directly, and routes every write through an approval.
The detailed pages below are written for the person who sets the connector up: which tools exist, which credentials and scopes to create, which actions need approval and where the limits are. They are added a few at a time, each researched against the platform's current documentation, and describe the connectors as they work in OrgRelay 1.4.0 or later.
Where a platform is missing, there are three other routes: OpenAPI import, GraphQL import, or connecting the vendor's own server as third-party MCP. For an in-house system, build a connector from the quickstart.
Detailed connector pages
E-commerce
| Connector | Read tools | Write tools | Typical questions |
|---|---|---|---|
| Shopify | 6 | 3 | Unshipped orders, low stock, sales for a period |
| WooCommerce | 6 | 3 | Orders by status, product prices, stock |
| Amazon Seller (SP-API) | 5 | 2 | Orders per marketplace, FBA inventory |
ERP and accounting
| Connector | Read tools | Write tools | Typical questions |
|---|---|---|---|
| Odoo | 7 | 2 | Sales orders, stock, receivables, purchase orders |
| QuickBooks Online | 4 | 1 | Overdue invoices, profit and loss |
| Xero | 4 | 1 | Invoices, receivables, profit and loss |
| Kingdee Cloud Galaxy (金蝶云星空) | 4 | 1 | Sales orders, inventory, receivables |
| LingXing ERP (领星) | 11 | 1 | Cross-border orders, FBA stock, profit by store |
CRM and support
| Connector | Read tools | Write tools | Typical questions |
|---|---|---|---|
| HubSpot CRM | 4 | 2 | Contacts, deals, tickets |
| Salesforce | 4 | 2 | Opportunities, accounts, cases |
| Zendesk | 3 | 2 | Open tickets by priority, ticket history |
Payments and SEO
| Connector | Read tools | Write tools | Typical questions |
|---|---|---|---|
| Stripe | 4 | 1 | Payments, balance, disputes |
| Google Search Console | 5 | 1 | Queries, page performance, URL inspection |
Tool names follow the standard tool names wherever a platform's data fits, so orders.search means the same thing on Shopify and on Amazon. That lets OrgRelay route tools to the right department agent and lets the AI compare answers across systems.
How every connector behaves
- Official APIs only. No scraping, no simulated logins. The company creates its own app or API key on the platform.
- Credentials stay on the company's machine, encrypted, with only the last four characters ever shown. See authentication.
- Reads run directly; writes wait for approval. Changing a price, adjusting stock, cancelling an order, creating an invoice or replying to a ticket always creates an approval request first. The rules are on approvals and write tools.
- Owners decide who uses what. A connection starts available to the owner only; the owner grants it to roles or departments and can switch off individual tools.
- Staff can use them from their own AI client through OrgRelay's MCP server, with the same permissions. See Claude Code and Codex.
What this means for the business, rather than the developer, is explained on orgrelay.com's integrations page.
All platforms
OrgRelay includes connectors for the following platforms. Setup instructions for each are inside OrgRelay under Admin → Business systems → App directory, in four languages.
| Category | Platforms |
|---|---|
| E-commerce and sites | Shopify, WooCommerce, WordPress, Adobe Commerce (Magento), Amazon Seller (SP-API), eBay, Etsy, Walmart Marketplace, Google Merchant Center, Mercado Libre, Shopee, Lazada, TikTok Shop / Tokopedia, 1688, Alibaba.com |
| ERP and accounting | Odoo, QuickBooks Online, Xero, SAP Business One, Kingdee Cloud Galaxy (金蝶云星空), Yonyou YonSuite (用友), LingXing ERP (领星) |
| CRM | HubSpot CRM, Salesforce, Pipedrive, Zoho CRM |
| Projects and support | Zendesk, Freshdesk, Jira, Asana, Trello |
| Office and collaboration | Google Workspace, Microsoft 365, Notion, Airtable, Feishu / Lark Base (飞书), DingTalk Yida (钉钉宜搭) |
| Payments | Stripe, PayPal, Wise, Airwallex, Payoneer |
| Logistics | UPS, DHL, FedEx, SF International (顺丰国际), Cainiao (菜鸟), ShipStation, 17TRACK |
| SEO and webmaster | Google Search Console, Bing Webmaster Tools, Baidu Search Resource Platform, Yandex Webmaster, Naver Search Advisor, Ahrefs, Semrush, SE Ranking, Moz, Similarweb |
| Analytics | Google Analytics 4, Matomo, Microsoft Clarity, Hotjar, Baidu Tongji |
| Advertising | Google Ads, Microsoft Advertising, Meta Ads, LinkedIn Ads, TikTok Ads, Amazon Ads, Baidu Marketing, Ocean Engine (巨量引擎) |
| Marketing | HubSpot Marketing, Klaviyo, Mailchimp, Brevo, Twilio |
| HR and signing | BambooHR, Workday, DocuSign, Adobe Acrobat Sign |
| Files and meetings | Dropbox, Box, Zoom, Google Meet recordings |
| Databases and files | MySQL, PostgreSQL and SQL Server (read-only), shared-folder import of Excel and CSV |
| Automation | Zapier, Make and n8n relay |
Choosing a route for a missing platform
| Situation | Route |
|---|---|
| Platform publishes an OpenAPI or Swagger file | OpenAPI import |
| Platform has a GraphQL API | GraphQL import |
| Vendor runs its own MCP server | Third-party MCP; see official MCP servers |
| In-house or heavily customised system | Build one from the code templates and check it with the self-test tool |
Related
- Connector spec and security requirements for anyone building a connector.
- Enterprise MCP patterns for rolling connectors out across a company.
- Human-in-the-loop for MCP on why writes wait for a person.