IT & cloud connectors
If It Speaks REST Or SOAP, You're Already Connected
Fuuz reaches the enterprise stack two ways: a purpose-built named connector where one exists — handling auth flows, versioning and formatting for you — and the standard HTTP connector everywhere else, which covers plain REST or SOAP over Basic or Bearer-token auth with no custom build. In practice, that second path is most of the modern enterprise stack, including every frontier LLM.
Purpose-built
Named Connectors
These are real, shipped Fuuz connectors — not adaptations. They handle authentication, pagination and payload shape for the platform they name.
HCM
Cloud, Data & Observability
eCommerce & POS
Quality & PLM
Shipping & Logistics
ERP
Manufacturing & Industry-Specific
Technology Connectors
Platform & Cross-Tenant
CRM
Nothing special needed
Speaks Basic Or Bearer-Token HTTP? You're Done
No named connector, no custom build, no waiting on a Fuuz release. If a system exposes a REST or SOAP API over Basic auth, a bearer token, an API key or OAuth2, the standard HTTP connector reaches it today — a data flow with an HTTP node and the vendor's own auth header. Every one of the following works this way right now.
PLM & PDM
HR & Workforce
ERP & Finance (generic HTTP)
Procurement & Planning
eCommerce, Payments & Logistics
Service, ITSM & Quality
Collaboration & DevOps
Cloud, Data & Observability
Featured — AI
Every Frontier Model
Fuuz is already connected to Claude.ai today over the standard HTTP connector — an API key, a REST call, streamed responses over SSE. The same path reaches every other frontier provider.
Anthropic ClaudeConnected today
Standard HTTP connector, API key auth, REST, SSE streaming. No named connector required — this is the live pattern Fuuz uses for Claude.ai now.
OpenAI (GPT-4, o-series)
OpenAI Chat — a purpose-built named connector, API key / bearer token auth. Token-based pricing; the Realtime API's WebSocket transport isn't reachable from the cloud connector.
Google Gemini / Vertex AI
Covered under the named Google API connector — OAuth2, REST — the same connector that reaches the rest of Google Cloud and Workspace.
Azure OpenAI
Standard HTTP connector, API key or Azure AD auth. No named connector required.
AWS Bedrock
Standard HTTP connector, AWS Signature V4, the InvokeModel API across every foundation model Bedrock hosts.
Meta Llama, Mistral, Cohere, Hugging Face
Standard HTTP connector; auth varies by provider (API key or bearer token). No named connector required for any of them.
Recently added
Two New Connectors
Körber PAS-X MSINew
A purpose-built named connector: publishes MSI messages (SF_TO_MES) to Körber PAS-X over its MSI Web Service. Outbound publish only, matching how PAS-X expects to receive shop-floor instructions — this is not a generic HTTP adaptation.
LM StudioNew
A self-hosted local model server with an OpenAI-compatible REST API. Reaches Fuuz over the same standard HTTP connector as any cloud LLM — point it at the LM Studio host's endpoint (typically on the local network, so no special auth is usually needed) and it's a drop-in swap for a cloud provider in a data flow.