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
Array of ADP Workforce Now API requests. Options include a `roleCode` header controlling the caller's visibility scope, and a `masked` flag (default true) that has ADP mask sensitive fields like SSN in the response.
Credentials
- Client ID required
- Client Secret required ● secret
Array of ADP Vista API requests (get/post only). Connection options (country, paymentUnit, legalEntity) are sent as request headers.
Credentials
- Client Id required
- Client Secret required ● secret
- Company Code required
- Login ID required
- Scope required
SAP SuccessFactors REST API requests (uppercase HTTP methods).
Credentials
- API Key required
- Company Id required
- Username required
- Private Key required ● secret
- Certificate required ● secret
- Issuer / Audiences / User Type optional
Cloud, Data & Observability
PutRecord / PutRecordBatch calls to a named delivery stream. Batch mode caps at 500 records per call.
Credentials
- Access Key ID required
- Secret Access Key required ● secret
- Session Token optional ● secrettemporary credentials only
Direct AWS SDK command invocations (InvokeCommand, ListFunctionsCommand, etc.) by name.
Credentials
- Access Key ID required
- Secret Access Key required ● secret
- Session Token optional ● secrettemporary credentials only
Array of Confluence REST API requests. Authenticated via Basic auth with email:apiKey.
Credentials
- Email required
- API Key required ● secret
Calls dispatched via the googleapis client — google[api]({version,auth})[resource][action](...). One connector reaches the entire Google Cloud and Workspace API surface.
Credentials
- Client Email required
- Private Key required ● secret
eCommerce & POS
callAPI / download / upload actions covering the Selling Partner API, report documents, and feed submission.
Credentials
- Client ID required
- Client Secret required ● secret
- AWS Access Key ID required
- AWS Secret Access Key required ● secret
- Selling Partner Role required
Array of ChannelAdvisor REST API requests.
Credentials
- Application ID required
- Shared Secret required
- Grant Type required
- Refresh Token required
- Redirect URL optional
Array of Clover REST API requests. `filters`, `expand`, `limit` and `orderBy` are serialized into Clover query parameters.
Credentials
- Authorization Token required ● secret
Array of Magento REST API requests. `filters` and `pagination` are serialized into Magento searchCriteria[...] query parameters.
Credentials
- Token optional ● secretToken, or Username + Password
- Username optional
- Password optional ● secret
QuickBooks Online REST API requests.
Credentials
- Client ID required
- Client Secret required ● secret
- Refresh Token required ● secretrotates periodically
Square REST API requests, with cursor-based pagination auto-followed by default.
Credentials
- Personal Access Token required ● secret
WooCommerce REST API requests (v2 or v3) against a WordPress site.
Credentials
- Consumer Key required
- Consumer Secret required ● secret
Quality & PLM
Array of Arena PLM REST API requests. Session token from credentials is sent as the `arena_session_id` header.
Credentials
- Username required
- Password required ● secret
- Client ID required
Shipping & Logistics
Array of C.H. Robinson (Navisphere) REST API requests.
Credentials
- Client ID required
- Client Secret required ● secret
- Audience optionaldefaulted
- Grant Type optionaldefaulted to client_credentials
read / write / ack / validate actions over X12 or EDIFACT EDI data.
Credentials
- OCP APIM Subscription Key required ● secret
Legacy FedEx SOAP API — Address Validation, Rates, Shipping Validation, Shipment Create/Delete, or a raw POST. Requests are XML, responses are parsed to JSON.
Credentials
- Client Detail — Account Number, Meter Number required
- User Credentials — Login Key, Password required ● secret
- Parent Credentials — Login Key, Password required ● secret
Modern FedEx REST API requests.
Credentials
- API Key (Client ID) required
- Secret Key (Client Secret) required ● secret
Fuuz-managed UPS requests plus license-management actions (License Agreement, License Request) alongside generic HTTP.
Credentials
- Access License Number optionalFuuz-managed UPS credentials — most fields are sourced from server config
Legacy UPS API. Action-based routing selects generic HTTP or pre-built flows (Address Validation, Create Shipment).
Credentials
- Username Token — Username, Password required ● secret
- Transaction Source required
- Service Access Token — Access License Number required ● secret
Modern UPS OAuth REST API requests — uses `action` (uppercase HTTP method) in place of `method`.
Credentials
- Client Id required
- Client Secret required ● secret
- Account Number required
USPS XML API calls (Verify, RateV4, etc.) — data is sent as an XML query parameter, not a request body; responses are parsed from XML to JSON.
Credentials
- User ID required
ERP
Array of Dynamics 365 REST API requests (uppercase HTTP methods). Covers F&O, Business Central, CRM and Dataverse under one connector.
Credentials
- Client ID required
- Client Secret required ● secret
- Scope required
Array of Infor ION API requests. Responses are inspected for Infor-specific error fields.
Credentials
- Client ID required
- Client Secret required ● secret
- Grant Type required
- Access Token URL required
- Username required
- Password required ● secret
- Scope optional
NetSuite REST/SuiteQL requests — uses `endpoint`/`action` in place of the common `path`/`method`.
Credentials
- Account ID required
- Consumer Key required
- Consumer Secret required ● secret
- Token ID required
- Token Secret required ● secret
NetSuite SuiteTalk SOAP operations by name (add, search, upsert, getList, async* variants, etc.).
Credentials
- Account ID required
- Consumer Key required
- Consumer Secret required ● secret
- Token ID required
- Token Secret required ● secret
Plex Connect API requests; tenant ID is sent as the X-Plex-Connect-Tenant-Id header.
Credentials
- Consumer Key required ● secret
Plex Classic datasource executions via SOAP, with key-based or offset-based pagination.
Credentials
- Username required
- Password required ● secret
Plex IAM API requests.
Credentials
- Client ID required
- Client Secret required ● secret
Plex UX (JSON REST) datasource execution or GET-mode metadata/search, with the same pagination options as Plex Classic.
Credentials
- Username required
- Password required ● secret
SAP Cloud OData requests — top/skip/filter/orderby/select/expand map to the OData $-prefixed query parameters.
Credentials
- Authorization Token required ● secret
Manufacturing & Industry-Specific
Generic REST requests against the FANUC Zero Down Time Data API (typically dataapi.fanuczdt.com).
Credentials
- API Key required ● secret
Publishes MSI messages (SF_TO_MES) to Körber PAS-X over its MSI Web Service — outbound publish only.
Credentials
- Username required
- Password required ● secretOAuth password-grant token request
Batches of typed rows converted to CSV, zipped and uploaded — REPLACE overwrites the dataset, MODIFY applies incremental changes.
Credentials
- Client Id required
- Client Secret required ● secret
- TecCom Id required
TecCom SOAP web service calls selected by function identifier.
Credentials
- User Name required
- Password required ● secret
Technology Connectors
FTP/FTPS/SFTP file operations — get, getAllInDir, post, put, delete, move, list. Required fields per operation are enforced by the connector.
Credentials
- Username required
- Password optional ● secretone of Password or SSH Key is required
- SSH Key optionalone of Password or SSH Key is required
- Passphrase optional ● secret
- Host Key / Host Key Hash optional
Generic REST calls — method, path, headers, body — against whatever endpoint the connection URL points at. Basic auth is optional; a bearer token or API key is sent as a header instead.
Credentials
- Username optional
- Password optional ● secret
Sequential SQL queries or stored procedure calls against a pooled connection, with typed parameter binding.
Credentials
- Username required
- Password required ● secret
SQL queries with `?` bind variables, executed in a worker pool against whatever ODBC driver the connection configures (Plex, NetSuite, etc.).
Credentials
- Username required
- Password required ● secret
- NetSuite OAuth block optionalOAuth URL, Account/Role/Client/Key ID, Private Key, signing algorithm — only when connecting to NetSuite over ODBC
Sends email via nodemailer — from/to/subject plus text or html, with attachments by inline content or URL reference.
Credentials
- Username required
- Password required ● secret
Platform & Cross-Tenant
Cross-tenant calls to another Fuuz instance — GraphQL query/mutation, run a data flow, a saved query, a saved script, or publish to a topic. Max 100 items per request.
Credentials
- Fuuz API Key required ● secret
GraphQL calls to a legacy MFGx instance.
Credentials
- Username required
- API Key required ● secret
CRM
Array of Salesforce REST API requests, with `pagination: true` to auto-follow nextRecordsUrl across pages.
Credentials
- Username required
- Password required ● secret
- Client ID required
- Client Secret required ● secret
Spiro REST API requests using JSON:API content type, with page-range pagination.
Credentials
- Authorization Token required ● secret
Zoho REST API requests, with `modifiedSince` and page-range pagination options.
Credentials
- Client ID required
- Client Secret required ● secret
- Authorization Token required ● secret
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. Full API reference & schema explorer →
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.