Connector classes

The current deployment is configured to reach the IntellaSwitch/FNI gateway for tenant-scoped connectivity. This connector is used for Keystone-style module calls and gateway health checks.

REST integrations require a base URL, optional bearer token, optional JSON headers, and manifest tools that specify method, path, query, and body. Production integrations should define rate limits and least-privilege credentials.

GraphQL integrations require an endpoint URL, optional bearer token, optional headers, and manifest-approved queries or mutations. Production deployments should prefer whitelisted operations and avoid broad introspection access.

Webhooks can connect Gizzy to Zapier, Make, n8n, serverless functions, or custom automation endpoints. Gizzy can sign outbound webhook payloads with an HMAC signature when a webhook secret is configured.

MCP integrations connect Gizzy to Model Context Protocol servers over HTTP. Gizzy calls approved MCP tools through the adapter layer while preserving session and idempotency metadata.

Custom adapters are appropriate when a client system needs specialized authentication, workflow rules, or safety boundaries. Custom adapters should avoid embedding secrets in source code and should enforce explicit read/write permissions.